Moved out (kept outside the repo, in the team's internal tracker): - AGENT-BRIEF.md: operating rules for the team's own agents - documentation/slide-deck-outline.md, documentation/README-longform.md: internal pitch material; the README and why.md cover the same ground - plugin-designs/gospel-resources/SOURCES-CHECKED-AND-REJECTED.md: research log - .claude/ (an editor status line), .forgejo/ (a CI workflow that never ran), _archive/ (a retired staging page; already gitignored but still tracked) Seven code comments that named these files now describe the rule instead. Fixed five dead links left from the docs/ -> documentation/ move, including the one in template-bundle that every new plugin inherits. The delegation diagram now shows the whole model: the Plugin Studio with the shared library and the merge queue into main, seven production plugins with capability badges and the Experimental shelf, one agent per plugin (a roaming agent for the shelf), the shepherd's oversight ring, a legend, and the five ways a build ships. |
||
|---|---|---|
| .. | ||
| api | ||
| colors | ||
| components | ||
| composables | ||
| utils | ||
| README.md | ||
src/ — your map's sandbox
Everything your map needs that isn't already in the shared library/ gets built here. Nothing in
this folder leaks to another map — build freely.
src/
├── api/ which API/CSV/endpoint this map reads
├── colors/ your colors: values (colors.json) + strategy .js files
├── components/ your map's own .vue pieces (not reusable)
├── composables/ your map's own logic hooks (useThing.js)
└── utils/ your map's own pure helpers
Two import styles, two meanings:
import { useMapInstance } from '@map/composables/useMapInstance.js' // reuse the shared library
import colors from './src/colors/colors.json' // your own sandbox (relative)
There is no @map/-style alias for your sandbox — your code is always relative. That boundary keeps
it private. Reusable + parameterized → library/ (an expert move); specific to this map → stays
here. Local by default.
Each subfolder has its own README. See also:
../README.md (build-a-map guide) ·
../../../documentation/reference.md (the @map/… menu).