Bind deployment trigger and commit identity

This commit is contained in:
Meta Vens 2026-07-13 05:12:09 +01:00
commit 2bc6ec6be2
7 changed files with 22 additions and 5 deletions

View file

@ -247,6 +247,8 @@ fn run_smoke(args: Args) -> Result<Value> {
"aftercare_audit = \"gamecult.idunn.deployment_aftercare_audit.v0\"",
)?;
require_text(&request_text, "requires_deployment_script_ref = true")?;
require_text(&request_text, "requires_watched_ref = true")?;
require_text(&request_text, "requires_source_commit_sha = true")?;
require_text(&request_text, "requires_script_hash = true")?;
require_text(&request_text, "requires_script_review_ref = true")?;
require_text(&request_text, "requires_host_access_policy_ref = true")?;

View file

@ -5586,7 +5586,8 @@ fn derive_repo_deployment_request_plan(
String::new(),
"[deployment_packet]".to_string(),
"requires_target_environment = true".to_string(),
"requires_git_ref_or_branch = true".to_string(),
"requires_watched_ref = true".to_string(),
"requires_source_commit_sha = true".to_string(),
"requires_deployment_script_ref = true".to_string(),
"requires_script_hash = true".to_string(),
"requires_script_review_ref = true".to_string(),
@ -13749,7 +13750,8 @@ idunn_deployment = "gamecult.idunn.deployment_receipt.v0"
aftercare_audit = "gamecult.idunn.deployment_aftercare_audit.v0"
[deployment_packet]
requires_target_environment = true
requires_git_ref_or_branch = true
requires_watched_ref = true
requires_source_commit_sha = true
requires_deployment_script_ref = true
requires_script_hash = true
requires_script_review_ref = true

View file

@ -479,7 +479,8 @@ pub(super) struct RepoDeploymentRequestReceipts {
#[derive(Debug, Deserialize)]
pub(super) struct RepoDeploymentRequestPacket {
pub(super) requires_target_environment: bool,
pub(super) requires_git_ref_or_branch: bool,
pub(super) requires_watched_ref: bool,
pub(super) requires_source_commit_sha: bool,
pub(super) requires_deployment_script_ref: bool,
pub(super) requires_script_hash: bool,
pub(super) requires_script_review_ref: bool,
@ -547,7 +548,8 @@ impl RepoDeploymentRequest {
pub(super) fn has_packet_contract(&self) -> bool {
let value = &self.deployment_packet;
value.requires_target_environment
&& value.requires_git_ref_or_branch
&& value.requires_watched_ref
&& value.requires_source_commit_sha
&& value.requires_deployment_script_ref
&& value.requires_script_hash
&& value.requires_script_review_ref

View file

@ -1427,3 +1427,9 @@ Deployment requests accepted `script_hash_or_review_ref`, treating byte
identity and approval as interchangeable. They now require both a script hash
and a script-review reference. The hash binds the reviewed bytes; the review
receipt carries judgment. Neither may impersonate the other.
Deployment also accepted `git_ref_or_branch`, obscuring the difference between
the mutable ref Idunn watches and the immutable commit it deploys. The Idunn
receipt contract already records both `watched_ref` and `source_commit`.
Deployment requests now require both fields: trigger topology and artifact
identity are conjunctive evidence.

View file

@ -529,3 +529,8 @@ public feedback rather than "human or Persona review"; Mind/Bifrost remain the
gates. Deployment requests require both script hash and script-review ref,
because identity and approval are distinct proofs. Continue classifying the
remaining OR-shaped fields by what invariant each alternative actually proves.
Deployment git identity is also split. Requests now require both watched ref
and source commit SHA, matching Idunn's receipt. A branch/ref identifies the
mutable trigger path; the commit SHA identifies deployed bytes. Do not collapse
them back into one convenient string.

Binary file not shown.

View file

@ -660,4 +660,4 @@ current_status:
- Service lifecycle receipt history is now event-only: `load_epiphany_cultmesh_daemon_service_lifecycle_receipts` filters out the `epiphany-local/daemon-service-lifecycle-receipt/latest` mirror, while `load_latest_epiphany_cultmesh_daemon_service_lifecycle_receipt` remains the latest-state reader. Focused unit test `service_lifecycle_receipt_history_excludes_latest_mirror` proves two per-receipt writes return exactly two history records and latest points at the second. Fresh smoke `verse-query-lifecycle-history-filter-smoke` and live overview/triage `local-20260618-145632-497-efac6f0d` / `local-20260618-145632-321-867947af` prove compact swarm sights still expose service lifecycle attention plus the present elevated runbook artifact without daemon pokes or service mutation. Do not use a broad unscoped cargo test filter for this check on Windows; it fans out across bin harnesses and hit a broken pipe during this pass.
- `epiphany-verse-query seed-compact` is the compact seed receipt for wrappers and read-only rites. The older `seed` command still prints the full local Verse context for explicit debugging, but compact wrapper modes now avoid full `seed`/final `query` readback after the combined overview proof exposed Windows debug stack overflow from full-context serialization pressure.
last_completed_repo_swarm_cut: Huginn live-fire has crossed the first real repo Body from Persona pressure to branch-local Hands commit and Soul/Mind closure, and now has repeatable closure and redacted-public-proof mouths. On `E:\Projects\Huginn` branch `epiphany/huginn/first-awakening`, `tools/epiphany_local_run.ps1 -Mode repo-persona-intake` accepted item `huginn-inspection-readback-livefire`, Weksa/Persona intake remained sealed, and `epiphany-work derive-plan` lowered it to model-authored safe family `repo.status_section` for `README.md` only. `tools/epiphany_local_run.ps1 -Mode repo-swarm-run` advanced four bounded pulses: run-from-plan, adopt-from-plan, execute-from-plan, and close-from-execute. Huginn commit `e9b07c38fceabbdc89ea35c2156326c80c0393a2` updated only `README.md`; closure receipt `.epiphany\work\work-close-huginn-inspection-readback-livefire.json` records status `closed`, Soul verdict `passed`, Mind state commit `repo-work-close-huginn-inspection-readback-livefire-mind-commit`, safe family `repo.status_section`, path scope `README.md`, Bifrost publication gate, and `privateStateExposed=false`. Verification also ran Huginn's TypeScript compiler through concrete Node path: `C:\Program Files\nodejs\node.exe E:\Projects\Huginn\node_modules\typescript\bin\tsc -p tsconfig.json` passed. Native verifier `epiphany-repo-livefire-closure-smoke --workspace E:\Projects\Huginn --item huginn-inspection-readback-livefire --expected-path README.md --expected-family repo.status_section --expected-gate awaiting-publication --expected-blocker bifrost-publication-missing` checks closure receipt, Mind map entry, overview gate/blocker, authority seals, and `git show` changed paths, returning `status=ok`, `soulVerdict=passed`, `publicationGate=Bifrost`, and `privateStateExposed=false`. Wrapper `tools/epiphany_local_run.ps1 -Mode repo-livefire-closure -Workspace E:\Projects\Huginn -RepoWorkItem huginn-inspection-readback-livefire -SkipBuild` exposes the same read-only proof through the local operator mouth; artifact `local-20260621-190156-803-2f85ba15` printed commit, path, gate, blocker, Soul verdict, Mind commit receipt, and `privateStateExposed=False` without push, merge, publication, or target mutation. New wrapper `tools/epiphany_local_run.ps1 -Mode repo-work-public-proof -Workspace E:\Projects\Huginn -RepoWorkItem huginn-inspection-readback-livefire -SkipBuild` exports the redacted proof bundle and repo-local Verse index without publishing; artifact `local-20260621-190645-345-4555b1dc` wrote `.epiphany\public\proof-bundles\repo-work-public-proof-huginn-inspection-readback-livefire.json`, proof id `repo-work-public-proof-huginn-inspection-readback-livefire`, SHA-256 `857545b199f3e37eb06c2e757e5cfc201958e46667bb1f8403fd333a22620f63`, nine artifact rows, zero publication rows, and `privateStateExposed=False`. swarm overview readback `local-20260621-190701-140-b9519ec6` sees the `REPO-WORK-PUBLIC-PROOF` row and action row from Huginn's repo-local Verse with the same SHA-256 while Bifrost publication remains missing. Launcher compact modes are now named compact operator-context modes instead of read-only modes, and `bifrost-public-proof` summaries print item, target public Verse, room, proof SHA-256, review receipts, and credit receipts so publication receipts are auditable without claiming upstream sync.
next_action: Continue the OR-field and observation-to-consequence audit. Consensus now asks for additional public feedback without granting review authority; deployment requires both script identity hash and review receipt. Classify remaining alternatives by invariant, then inspect status/receipt/scheduler/cache projections for borrowed closure or effect authority. Keep closure's zero-substring invariant.
next_action: Continue the OR-field and observation-to-consequence audit. Deployment now requires watched ref plus immutable source commit, and script hash plus review receipt; trigger topology, byte identity, and approval are separate proofs. Classify remaining alternatives by invariant, then inspect status/receipt/scheduler/cache projections for borrowed closure or effect authority. Keep closure's zero-substring invariant.