Skip to content

feat: hermetic branch-N replay runner (MRR-ITE) - #1

Open
fraware wants to merge 31 commits into
mainfrom
feat/hermetic-branch-n
Open

feat: hermetic branch-N replay runner (MRR-ITE)#1
fraware wants to merge 31 commits into
mainfrom
feat/hermetic-branch-n

Conversation

@fraware

@fraware fraware commented Jul 25, 2026

Copy link
Copy Markdown
Member

Summary

  • Delivers the MRR-ITE hermetic branch-N runner stack as 31 focused commits: scaffolding, schemas, providers, hermeticity, scheduling, accounting, differentials, PCS/PIP evidence, CLI wiring, tests, offline CI, docs/ADRs, scripts, and Docker.
  • Vendors ExecutionProfile, branch manifest, resource/differential report, PCS, and PIP schemas with offline fixtures and validators.
  • Adds unit, hermetic, adversarial, conformance, and integration suites plus an offline CI workflow; Morph replay remains optional and lean.

Test plan

  • Confirm CI workflow passes on this branch (lint/typecheck/tests offline)
  • Run unit + hermetic suites locally without Morph credentials
  • Spot-check examples/hermetic-branch-n against the documented flow
  • Review ADRs 00-09 and SECURITY/NON_CLAIMS for accuracy before merge
  • Merge only after review (do not auto-merge)

fraware added 30 commits July 24, 2026 23:27
Pin project metadata and dependencies, add LICENSE, and stop tracking egg-info so local installs stay out of version control.
Establish the architectural decision record and baseline notes so later slices have a shared design anchor.
Define the vendored MRR execution profile contract used to pin hermetic replay inputs.
Provide typed profile parsing against the schema with valid and invalid fixtures for offline checks.
Introduce a provider interface so replay orchestration can swap Morph for a deterministic local fake.
Wire the Morph SDK-backed adapter behind the shared provider interface for real remote replay runs.
Encode offline and isolation mode checks so runners can refuse non-hermetic configurations early.
Define the multi-branch intervention manifest contract for hermetic branch-N schedules.
Implement manifest parsing and branch-N scheduling against fixtures so multi-intervention replays stay deterministic.
Capture the accounting contract for CPU, memory, and network usage emitted by replay runs.
Aggregate per-branch resource measurements into schema-aligned reports for cost and capacity analysis.
Define the contract for comparing branch outcomes against a baseline replay.
Compare branch artifacts against a baseline and emit schema-valid differential summaries.
Include RuntimeReceipt and ArtifactIntegrity schemas so evidence emission stays offline-validatable.
Generate PCS receipts from replay runs and validate instances against the vendored schemas.
Add TransformationRecord, LineageBundle, and MorphReplayReport contracts with mirror metadata.
Produce MorphReplayReport and LineageBundle artifacts and ship valid linkage fixtures for conformance tests.
Centralize stable hashing used by manifests, snapshots, and evidence linkage.
Reserve the OVK integration surface so optional verification hooks can land without reshaping imports.
Refactor entrypoints to use profiles, providers, and evidence paths; keep legacy core available for compatibility.
Exercise import smoke, accounting, diff, PCS, profile, and provider modules offline.
Verify mode gates and branch-N scheduling against fixtures without network access.
Cover secret isolation, schema instance validity, PIP linkage, and offline CI gate scripts.
Run lint, typecheck, and hermetic tests without Morph credentials; keep replay workflow optional and lean.
Clarify non-claims, threat model, release checklist, and changelog so operators know what the runner does and does not assert.
Record decisions for profiles, providers, hermeticity, scheduling, resources, differentials, PCS, PIP, and release security.
Explain vendored MRR/PCS/PIP schemas and how offline fixtures map to conformance tests.
Ship a copyable profile, manifest, interventions, and snapshot refs for local branch-N demos.
Keep vendored schema mirrors honest and validate fixture instances offline before release.
Automate fixture refresh and produce a reproducible release artifact tree for distribution.
Align the container build and compose wiring with the new package layout and offline defaults.
@cursor

cursor Bot commented Jul 25, 2026

Copy link
Copy Markdown

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant