Skip to content

Register Phase 4 continuation after an independently accepted native audit #2114

Description

@realmarcin

A separately completed native audit does not yet have a registered successor for reconciling the frozen full record, deriving its final core, and producing a checked report. The existing audit controller is explicitly Phase 3 only; the standard generation provenance describes one session and cannot represent a continuation honestly.

Add a separate Phase 4 condition that requires independent acceptance of the exact audit, reuses the shared reconciliation/report instruments, and preserves all originals. Track final writes, deterministic core derivation and typed checker results, invalidate stale checks, and retain the existing terminal evidence-failure and report-repair rules. Record composite generation/audit/reconciliation provenance without claiming uninterrupted generation.

Consume the current predecessor under an atomic shared-budget handoff so a sibling audit/reconciliation cannot spend the same remaining allocation. Pin the settled checkpoint, code, inputs, output paths, transport and attempt cap. Complete independent final-pair/report acceptance before handing off to evaluations.

Reuse api_runner.build_phase, derive_core, pair/schema/term validation, report claims and evidence assertions. Add offline success, stale-evidence, sibling-admission and failure-path tests. This issue records missing implementation; it does not assert that any current audit has passed.

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