Skip to content

Projection-parity gate: prove analysis.json and the Neo4j graph agree #37

Description

@rahlk

Parent: #35 · Roadmap: docs/design/roadmap.md (candidate 3)

Skeleton — bodies to be filled in by the maintainer.

Problem

Canonical v2 states analysis.json and the Neo4j graph are two projections of one structure that must agree. Nothing checks this in any analyzer. codeanalyzer-typescript demonstrably violates it: structured TSDecorator (.claude/SCHEMA_DECISIONS.md #4) and TSApplication.entrypoints are in its invariant spine and reach analysis.json, but neither appears in its Neo4j label table.

Scope boundary

Proves the two projections agree for the same run. Does not check either projection against canonical v2 — that is the conformance suite.

Goals

  • TODO
  • Home repo for the gate decided (blocked on the contract spec)

Caveats and known risks

  • TODO

Definition of done

  • TODO — must fail on today's codeanalyzer-typescript before it passes.

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