Component Name
Purpose
Replace this callout with a concise explanation of what the component does and why it exists.
Description
Write the high-level description here. Include whether the component belongs to the desktop app, CLI, VS Code extension, Juno mod, documentation, or test/verification tooling.
Responsibility
| Responsibility | Notes |
|---|---|
| Primary behavior | |
| Inputs | |
| Outputs | |
| Failure modes |
Methods / API
| Method or endpoint | Signature | Description |
|---|---|---|
Dependencies
| Dependency | Reason |
|---|---|
Notes
Documentation rule
Link to related notes with wikilinks so the graph stays connected.
Validation rule
If this component affects export output, link to 04 - Export Validation and document the validation impact.
Checklist
- Identify owner surface: app, CLI, extension, mod, or docs.
- Add links to at least two related notes.
- Add the note to Component Map if it documents a project script.
- Use canonical tags from Tag Taxonomy.
- Document inputs and outputs.
- Document validation or troubleshooting impact if relevant.
Backlinks
Related notes: 01 - Project Architecture, Component Map, Tag Taxonomy, 13 - Recommended Workflows, 14 - Troubleshooting.