Skip to content

backlog (entity)

Generated from solutions/ontological/lib/model/entities/backlog/schema.ts.

Schema version: 2.

A Backlog item is a stray idea captured before triage — deliberately unstructured, cheap to write, parked until someone decides whether it becomes real work. Two usage patterns coexist: a multi-item dump file (ideas struck through or deleted as they move on) and a single-candidate file (the whole file is one idea; on promotion it becomes an archive pointer to the artifact it produced).

A Backlog item is not:

  • A Task. A Task has a spec and is dispatchable; a backlog item earns that shape at promotion.
  • A Milestone. Same boundary, larger grain.
FieldTypeRequiredDescription
typestringArtifact type — used by the frontmatter validator to dispatch to this schema. Optional today (the validator falls back to the parent directory name).
schema_versionstringNumeric string version of the per-type schema this instance conforms to. Compare numerically when ordering versions. Independent of any product version. The value 0 is a documented sentinel meaning ‘pre-SDLC-managed’ — audit treats it as intentional, not stale. Optional in frontmatter: never in any per-type required set (audit flags a MISSING stamp as drift, not the validator).
idstringImmutable identifier per D-0002-entity-identifier-shape: ‘B-’ + 4 base-36 chars [0-9A-Z]. Matches the filename; never renamed once assigned. Optional on legacy multi-item dump files.
statusstringLifecycle stage. Absent means the file is still a raw idea or an ongoing dump. promoted/<entity> records that this backlog file was turned into a real artifact; pair with result:. closed/<reason> records discard without promotion.
titlestringHuman-readable headline. Frontmatter is canonical; the body opens with # <title> for readability.
createdstringISO date the entity was first authored.
last_reviewedstringISO date the entity was last reviewed. Optional: never in any per-type required set.
relatedarrayCross-references to other entities as wikilinks (slug optional per D-0002-entity-identifier-shape). Each per-type schema may add an items.pattern constraint narrowing the admissible link shapes.
tagsarrayFree-form labels. Required at the common level, defaulting to []. Per-type schemas may add a contains constraint (e.g. Principle requires exactly one principle/<category> tag).
need_human_reviewbooleanReview-tracking flag.
likely_typestringNon-binding triage hint: the entity-type slug this item will likely become (task, milestone, decision, driver, …). Recorded by the triager; never constrains the promotion outcome — status/result record what actually happened.
resultstringWikilink to the artifact this backlog file resolved to. Required when status: starts with promoted/ or is closed/duplicate. The conditional rules narrow result:’s pattern to match the specific status: value.
  • promoted/task
  • promoted/milestone
  • promoted/decision
  • closed/abandoned
  • closed/duplicate