up:: Projects MOC
owner:: @Niko
intent: living-doc
llm: update-in-place
scope: team
One paragraph: what this project is, and links to its parent system + sibling notes.
skills::
lead:: ThisCouldBeYou!
start::
estimated completion::
season::
Brief overview of the project.
What the project aims to achieve and its relevance to La Finka's mission.
Specific goals the project intends to accomplish.
Historical context or preliminary data that led to the project.
Unmade choices that block progress. Keep them in one table instead of scattered through prose, so nothing gets procured against a decision that was never made. Resolve by editing the row's Status, then fold the outcome into the section it affects.
These are engineering / scope forks inside this project. Vault-wide structural choices go to _resources/_meta/Open Decisions.md instead — different surface, don't mix them.
| # | Decision | Options | Status |
|---|---|---|---|
| D-1 | What has to be chosen | (a) … (b) … | Open |
What is and isn't included.
Container for engineering detail — diagrams, wiring, one-lines, terminal maps, layouts, component tables. Nest it all as ### under here rather than adding a sixth top-level H1; the five # Project - … headings are the note's stable skeleton and MOC queries depend on them.
The priced bill of materials lives in exactly ONE place, and the other section points at it. Default home is # Project - Resources → ## Materials & Tools. But when the parts table is inseparable from its costing rationale — amortisation, a cost lever, a superseded-pricing note — keep it here and make Materials & Tools an acquisition checklist that points back. Either way, prices stated twice will fork; that is the actual failure, not which section wins. (Both of the vault's heavy notes had forked this way.)
Description
Description
Description
Links or embedded media showing progress or highlights.
Links to relevant documents — plans, blueprints, research papers.
How community members can participate or contribute.
[!note]- Template conventions — delete this callout when filling the template
Headings use hyphens, not em dashes (# Project - Overview). Every project note in the vault uses hyphens; matching them keeps headings greppable and anchor links stable.
The five # Project - … H1s are the skeleton — don't add a sixth. Overview · Details · Resources · Documentation and Media · Collaboration and Participation. Depth that doesn't fit goes under ## Design inside Details. Inserting a new top-level H1 is the single most common drift in this vault's heavy notes.
project/build is load-bearing. Projects MOC filters its Builds queries on type: project and the project/build tag. A project note without that tag will not appear in the MOC, no matter where it lives. The MOC's "Water Projects" query is additionally scoped to the Projects/ folder — notes filed in Land/LivingLab/ must also be added to the MOC's manual Related list to be reachable.
Add your own domain tags. The frontmatter ships only the two load-bearing tags. Add the cross-cutting domain/* and section tags this project actually needs (domain/water, land/garden, community, maintenance/hvac, infrastructure, …) — see _resources/_meta/taxonomy.md. Do not inherit a domain tag you haven't checked.
Inline fields go directly after the Meta callout , lead::, start::, estimated completion::, season:: — this is where the vault's existing project notes put them.
season:: claims membership in a quarter's focus — season:: Quarterly Reports § Conventions.
If you are creating a project inside an active focus, set it now — a season assembles its report from these, and cannot recover a membership nobody claimed.
status must be one of the taxonomy values: idea → draft → active | planned → doing → done, plus review, paused, archived. See _resources/_meta/taxonomy.md.
updated: YYMMDD — stamp it whenever you make a substantive revision.
Routing. Community-facing property builds → Projects/ with up:: Projects MOC. Experimental land-tech builds (irrigation, KNF, smart systems) → Land/LivingLab/ with up:: [[LivingLab MOC]] and dg-publish: false.
## Open Decisions and ## Design are optional — an idea-stage note should delete both. Add them when a project reaches planned / doing and starts carrying real engineering weight. Worked examples: Project - Basement Control (Geo & Furnace) and Project - Water Flow Tracking.
Two callout idioms go with them. Use these instead of deleting an approach or leaving a stale one in place:
> [!warning] Superseded design
> An earlier revision used X. Superseded by Y because <reason>. Revive only if <condition>.
> [!missing] Not yet drawn — this is Milestone A
> What the artifact must define, and what is blocked until it exists.
The first keeps a dropped approach auditable without letting its bill of materials linger and contradict the live one. The second stops an empty heading from reading as finished work.
Created: 260920-14:29
Updated: 260920-14:29