Skip to content

[TASK-001]: Fix graph.tri — add missing spec declarations, fix typo #8

Closed

Description

@gHashTag

Graph Topology Cleanup (LAW 8 Violations)

Found during Ring-0 post-merge audit (see #2 comment).

Must Fix (P0)

  1. Fix typo in phi_critical_edges (line 372):
    triatt-sacredred → triatt-sacred

  2. Add 7 AR spec declarations to architecture/graph.tri:

    Spec ID Path Tier
    triar-logic specs/ar/ternary_logic.t27 2
    triar-proof-trace specs/ar/proof_trace.t27 2
    triar-datalog specs/ar/datalog_engine.t27 2
    triar-restraint specs/ar/restraint.t27 2
    triar-explainability specs/ar/explainability.t27 2
    triar-asp specs/ar/asp_solver.t27 2
    triar-composition specs/ar/composition.t27 2
  3. Add 8 GF numeric spec declarations:
    gf4, gf8, gf12, gf20, gf24, gf32, goldenfloat_family, phi_ratio

Should Fix (P1)

  1. Add 9 compiler tooling specs to graph.tri:
    compiler/ast.t27, compiler/cli/gen.t27, compiler/cli/git.t27, compiler/cli/spec.t27, compiler/codegen/testgen.t27, compiler/codegen/zig/runtime.t27, compiler/runtime/commands.t27, compiler/runtime/validation.t27, compiler/skill/registry.t27

  2. Add specs/compiler/parser.t27 to graph.tri

  3. Reconcile docs/SEED-RINGS.md layer table with Constitutional LAW 3 ranges

Acceptance Test

# Every .t27 file in specs/ and compiler/ must have a matching spec{} block in graph.tri
# Every spec referenced in edges{} must have a spec{} declaration
# No dangling references in phi_critical_edges or sacred_core_edges

φ² + 1/φ² = 3 | TRINITY

Activity

  1. added a commit that references this issue on Apr 4, 2026
    bb3dac0
  2. added 4 commits that reference this issue on Jun 1, 2026
    95563b3
    0325563
    4d4d65c
    4e95371
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

    documentationImprovements or additions to documentation

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions