morluto/rea

Fork 0

mirror of https://github.com/morluto/rea.git synced 2026-11-05 06:45:22 +00:00

[GH-ISSUE #72] Regenerate evidence and completion ledgers automatically #59

New issue

Closed

opened 2026-10-15 18:20:37 +00:00 by bsakaguchi · 4 comments

bsakaguchi commented

2026-10-15 18:20:37 +00:00

Owner

Originally created by @morluto on GitHub (Jul 12, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/72

Problem

Hand-maintained counts, manifests, and completion ledgers drift from artifacts and verifier results.

Outcome

Make verifiers the sole source of deterministic generated manifests, evidence indexes, and completion summaries, with CI check mode.

Scope

Immutable input manifests contain artifact hashes, scenario versions, providers, and environments. Generate pass/fail/unsupported/truncated/unknown separately and link every claim to evidence IDs. Regenerate in a temporary root and diff tracked metadata. Keep manual narrative separate.

Safety

Never emit secrets, private paths, credentials, or unsanitized captures. CI cannot rewrite branches. Missing evidence invalidates old claims.

Acceptance criteria

One command regenerates deterministically; CI fails on artifact/scenario/provider/schema/count drift, deletion, tampering, or stale skills; unsupported/unknown never count as pass; output is path-independent.

Dependencies

Parent #24. Requires Evidence v2 bundles and semantic conformance.

Verification

Clean/check modes, all drift classes, deletion, sanitization, ordering, interruption, concurrency, and manual tampering.

Non-goals

Narrative generation, storing large captures in Git, or treating test counts as fidelity.

Originally created by @morluto on GitHub (Jul 12, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/72 ## Problem Hand-maintained counts, manifests, and completion ledgers drift from artifacts and verifier results. ## Outcome Make verifiers the sole source of deterministic generated manifests, evidence indexes, and completion summaries, with CI check mode. ## Scope Immutable input manifests contain artifact hashes, scenario versions, providers, and environments. Generate pass/fail/unsupported/truncated/unknown separately and link every claim to evidence IDs. Regenerate in a temporary root and diff tracked metadata. Keep manual narrative separate. ## Safety Never emit secrets, private paths, credentials, or unsanitized captures. CI cannot rewrite branches. Missing evidence invalidates old claims. ## Acceptance criteria One command regenerates deterministically; CI fails on artifact/scenario/provider/schema/count drift, deletion, tampering, or stale skills; unsupported/unknown never count as pass; output is path-independent. ## Dependencies Parent #24. Requires Evidence v2 bundles and semantic conformance. ## Verification Clean/check modes, all drift classes, deletion, sanitization, ordering, interruption, concurrency, and manual tampering. ## Non-goals Narrative generation, storing large captures in Git, or treating test counts as fidelity.

bsakaguchi

2026-10-15 18:20:37 +00:00

closed this issue
added the
P1: high

roadmap

documentation

enhancement

area: tests
labels

bsakaguchi commented

2026-10-15 18:20:38 +00:00

Author

Owner

@morluto commented on GitHub (Jul 17, 2026):

Current main has deterministic generated catalog, package metadata, TypeDoc, schemas, and fixture-manifest infrastructure. The missing outcome is a verifier-produced Evidence v2 completion ledger that records pass/fail/unsupported/truncated/unknown and invalidates stale evidence. Reuse the existing generated-file framework.

@morluto commented on GitHub (Jul 17, 2026): Current main has deterministic generated catalog, package metadata, TypeDoc, schemas, and fixture-manifest infrastructure. The missing outcome is a verifier-produced Evidence v2 completion ledger that records pass/fail/unsupported/truncated/unknown and invalidates stale evidence. Reuse the existing generated-file framework.

bsakaguchi commented

2026-10-15 18:20:38 +00:00

Author

Owner

@morluto commented on GitHub (Jul 17, 2026):

Current-main audit: generated package metadata, product catalog, conformance fixture manifests, freshness checks, and verifier JSON summaries are delivered. Remaining scope is a verifier-produced Evidence v2 completion ledger with deterministic pass/fail/unsupported/truncated/unknown records and drift-checked regeneration. Existing ad-hoc summaries do not satisfy that contract, so this issue remains open.

@morluto commented on GitHub (Jul 17, 2026): Current-main audit: generated package metadata, product catalog, conformance fixture manifests, freshness checks, and verifier JSON summaries are delivered. Remaining scope is a verifier-produced Evidence v2 completion ledger with deterministic pass/fail/unsupported/truncated/unknown records and drift-checked regeneration. Existing ad-hoc summaries do not satisfy that contract, so this issue remains open.

bsakaguchi commented

2026-10-15 18:20:39 +00:00

Author

Owner

@morluto commented on GitHub (Jul 20, 2026):

Split into focused child issues:

#386
#387

These replace the broad remaining scope in this issue. Closing this parent can happen once all children are closed.

@morluto commented on GitHub (Jul 20, 2026): Split into focused child issues: - [ ] #386 - [ ] #387 These replace the broad remaining scope in this issue. Closing this parent can happen once all children are closed.

bsakaguchi commented

2026-10-15 18:20:39 +00:00

Author

Owner

@morluto commented on GitHub (Jul 22, 2026):

Completed by #408 (merge commit c02d33f). Its declared child issues #386 and #387 are closed, and main now has deterministic Evidence v2 completion-ledger generation plus CI drift checks with pass/fail/unsupported/truncated/unknown kept distinct.

@morluto commented on GitHub (Jul 22, 2026): Completed by #408 (merge commit c02d33f). Its declared child issues #386 and #387 are closed, and main now has deterministic Evidence v2 completion-ledger generation plus CI drift checks with pass/fail/unsupported/truncated/unknown kept distinct.

bsakaguchi referenced this issue

2026-10-15 18:22:05 +00:00

[GH-ISSUE #332] Capture event-complete process-tree lifecycle #178

bsakaguchi referenced this issue

2026-10-15 18:22:05 +00:00

[GH-ISSUE #333] Integrate event-backed process-tree capture into Process Capture v4 #179

bsakaguchi referenced this issue

2026-10-15 18:24:08 +00:00

[GH-ISSUE #788] [Docs] Clarify Windows Process Capture support and PTY recovery advice #344

bsakaguchi referenced this issue

2026-10-16 21:05:48 +00:00

[GH-ISSUE #3796] [Tracker] Open feature requests by area (October 2026) #1471