Skip to content

ADR 0004 (1/15): Artifact census + classification manifest gate [AFK] #21

Description

@Spelkington

Parent

#20

What to build

Foundation for the whole initiative. Enumerate every artifact under tests/**/Fixtures, **/Data/_08_Reporting, dumps/, libs/**/*.json and classify each as Evidence / Derived / architectural-decision into a manifest.

Per the ADR's production rule: the census itself is a Flowthru flow landing in _08_Reporting (Flowthru is the analytics backbone — a census living anywhere else is itself a hand-rolled artifact). The gate over its output is NUnit.

Expect to surface forgotten artifacts. known-families.json, families.json, and blood-artist-engine.json are still referenced by the InteractionTriage flow despite ADR 0003 Stage 0b calling for their retirement once witnessed.

Acceptance criteria

  • A Flowthru flow enumerates and classifies every artifact into a manifest in _08_Reporting
  • NUnit gate: an unclassified artifact fails the build — a stateless invariant (every artifact must be classified), never a shrink-only count
  • The gate is proven by adding a new unclassified artifact and observing a red build
  • Genuinely ambiguous artifacts are flagged for human classification rather than guessed
  • Full CORE ring green

Blocked by

None — can start immediately.

No activity

Activity on this issue will appear here.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions