generated from coulomb/repo-seed
one time bootstrap path
This commit is contained in:
@@ -42,6 +42,20 @@ normalization.
|
||||
facts or to lower-level characteristics.
|
||||
- Observed fact: deterministic scanner output such as files, manifests,
|
||||
languages, tests, APIs, routes, commands, or documentation references.
|
||||
- Intent: a design-time statement of expected repository utility. `INTENT.md`
|
||||
is the preferred file for this. It can guide candidate generation because it
|
||||
describes why the repository should exist.
|
||||
- Derived scope: a current-state statement of what the repository is understood
|
||||
to provide. `SCOPE.md` is the preferred file for this. It is generated or
|
||||
curated from evidence and approved characteristics, so it should not be used
|
||||
as ordinary evidence for rebuilding those same characteristics.
|
||||
- Intent bootstrap: a one-time migration that creates `INTENT.md` from an
|
||||
existing `SCOPE.md` when no intent file exists. The generated file carries a
|
||||
provenance note and should be reviewed as design intent.
|
||||
- Source role: provenance metadata on a fact or content chunk, such as
|
||||
`intent_summary`, `derived_scope`, `product_documentation`,
|
||||
`implementation_source`, `dependency_declaration`, `configuration`,
|
||||
`ci_tooling`, `test_evidence`, or `agent_guidance`.
|
||||
- Candidate: proposed characteristic or evidence from deterministic heuristics
|
||||
or optional LLM assistance. Candidates are review inputs, not registry truth.
|
||||
- Approved: curated registry truth that appears in ability maps, search, exports,
|
||||
|
||||
Reference in New Issue
Block a user