engineering-process 0.5.0__tar.gz → 0.6.0__tar.gz

{engineering_process-0.5.0/engineering_process.egg-info → engineering_process-0.6.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: engineering-process
-Version: 0.5.0
+Version: 0.6.0
 Summary: Agent-neutral end-to-end engineering lifecycle and deterministic process CLI
 License-Expression: MIT
 Project-URL: Homepage, https://github.com/phuongnse/engineering-process
@@ -92,9 +92,10 @@ distribution: the POSIX backend owns a new process session/group and the Windows
 backend owns a kill-on-close Job Object. Consumer manifests, evidence, and exit codes
 do not branch by operating system. If an outer Windows Job applies incompatible
 nesting or UI limits, target creation fails closed instead of running uncontained.
-After a command root exits, both backends allow at most 250 milliseconds for child
-accounting to drain naturally. A process still present after that bound is terminated
-and makes the command fail; commands with no remaining child return immediately.
+After a command root exits, the POSIX backend allows at most 250 milliseconds and the
+Windows Job Object backend allows at most 5 seconds for child accounting to drain
+naturally. A process still present after its platform bound is terminated and makes
+the command fail; commands with no remaining child return immediately.
 
 This task boundary intentionally separates finite commands from services and
 interactive protocols. `processctl exec`, requirement probes, setup command actions,
@@ -480,12 +481,77 @@ may authorize installing that policy but never substitutes for a missing policy.
 When new evidence exposes multiple materially valid directions or would change
 accepted scope, owner, trust boundary, authority, compatibility, rollout, or
 lifecycle order, the coordinator stops dependent mutation and asks the project owner.
-It presents evidence, the invariant, real options, trade-offs, and a recommendation;
-the accepted decision is recorded before work resumes. Bounded implementation details
+Before presenting a material recommendation, it records every hard invariant,
+assumption, and option in a bounded recommendation artifact. `processctl` derives the
+valid, invalid, and unproven sets; cost or minimal-change optimization applies only to
+the complete valid set. A distinct actor and fresh context independently challenge
+assumption evidence, invariant tracing, option classification, and terminal ordering.
+If the exact digest-bound chain is not approved or contains no valid option, the
+result is blocked rather than a recommendation. Bounded implementation details
 already decided by the contract continue autonomously.
 
+Validate the recommendation, challenge, and optional owner resolution as one chain:
+
+~~~text
+processctl contract validate --kind recommendation recommendation.json
+processctl recommendation review start --project-root . \
+  --recommendation recommendation.json \
+  --actor <reviewer> --context <fresh-context> --actor-kind agent \
+  --method isolated-context --attested-by <host> \
+  --attestation-evidence <bounded-attestation>
+processctl contract validate --kind recommendation-review-assignment \
+  .process/runs/recommendations/<decision-id>/review-request-<ids>.json
+processctl contract validate --kind recommendation-review recommendation-review.json
+processctl recommendation validate-chain --project-root . \
+  --recommendation recommendation.json \
+  --assignment .process/runs/recommendations/<decision-id>/review-request-<ids>.json \
+  --review recommendation-review.json
+processctl recommendation resolution --project-root . \
+  --recommendation recommendation.json \
+  --assignment .process/runs/recommendations/<decision-id>/review-request-<ids>.json \
+  --review recommendation-review.json \
+  --selected-option <valid-option-id> --owner-id <owner-id> \
+  --owner-evidence-sha256 sha256:<digest> \
+  --selection-rationale-sha256 sha256:<digest> \
+  --output recommendation-resolution.json
+processctl recommendation validate-chain --project-root . \
+  --recommendation recommendation.json \
+  --assignment .process/runs/recommendations/<decision-id>/review-request-<ids>.json \
+  --review recommendation-review.json \
+  --resolution recommendation-resolution.json
+~~~
+
+The review-start command reserves the context across lifecycle and recommendation
+reviews before emitting its exact assignment. Resolution creation refuses symlinked,
+existing, or concurrently created output instead of redirecting or replacing it. The
+resolution records a selected valid option but grants no lifecycle completion, merge,
+release, deployment, or adoption authority. Those owning gates remain separate. The
+accepted decision is recorded before dependent work resumes.
+
+When a schema-3 change selects a project-owned `requiredEvidence` id, local profiles
+alone do not advance it to review. Create the exact no-authority request, run the
+project adapter, and ingest the complete supplemental set first:
+
+~~~text
+processctl change remote request --project-root . --change-id issue-123 \
+  --actor worker --context worker-session --actor-kind agent
+python verification/run_remote_verification.py --project-root . \
+  --change-id issue-123 --actor worker --context worker-session \
+  --actor-kind agent --repository owner/repository \
+  --failure-output /durable/receipts/issue-123-remote-failure.json
+processctl change status --project-root . --change-id issue-123
+~~~
+
+The adapter publishes a uniquely named exact-checkpoint verification tag, never a
+branch or PR, dispatches the protected-base workflow, validates service and bundle
+digests, calls `change remote ingest`, and deletes the tag in every terminal path.
+Downloaded temporary archives are deleted after ingestion; failed evidence is moved
+to the explicit durable failure location before cleanup. Remote artifacts and their
+service ids remain lifecycle evidence, not merge, release, deployment, or adoption
+authority.
+
 The canonical publication order is stricter than a PR-first workflow: implementation
-and every required profile pass on a clean checkpoint; a consumer-selected independent
+and every required local and remote profile pass on a clean checkpoint; a consumer-selected independent
 agent or human semantically reviews that checkpoint; findings repeat implementation,
 complete verification, and fresh review until approved; `change finish` records
 completion; only then may automation push and create the PR. Static policy/secret/pin
@@ -717,7 +783,8 @@ fingerprint, source tree, or publication range.
   exclusively by their hash-locked `requirements/process.txt`. The action invokes the
   producer-owned installer from its immutable action checkout and never downloads or
   executes helper source from the consumer branch.
-- Versioned JSON schemas define change, plan, verification, review, lifecycle,
+- Versioned JSON schemas define change, plan, verification, review, recommendation,
+  independent recommendation assignment and challenge, owner resolution, lifecycle,
   completion-related artifacts, release-change fragments, and the release
   classification contract. The generated Release PR gate binds that contract to the
   exact SemVer increment, package version, latest reachable prior tag, reviewed head,

{engineering_process-0.5.0 → engineering_process-0.6.0}/PRODUCTION_STANDARD.md

@@ -71,6 +71,16 @@ are preserved with review evidence. These reports supplement the public N-1
 lifecycle authority; code under verification never promotes itself to lifecycle
 authority.
 
+Projects declare named remote requirements and their exact profile and
+platform/runtime selector sets; change contracts select requirement ids. A lifecycle
+request binds those expanded requirements to one clean checkpoint, comparison base,
+workspace fingerprint, and immutable base-owned workflow checkpoint without granting
+review or delivery authority. Provider adapters remain project-owned and transport
+only the exact request. Core ingests local artifact bytes, verifies service and
+content digests plus one-to-one selector coverage, and keeps the lifecycle
+implementing until every local profile and remote requirement passes. A provider job
+conclusion or later PR check is not lifecycle evidence by itself.
+
 ## Failure to invariant
 
 A validated command, gate, release, adoption, or external-integration failure must
@@ -97,6 +107,27 @@ failure. Source, branch, version, credentials, and controls are never changed me
 to cause another attempt. Independent review treats violation of these ownership and
 evidence boundaries as completion-blocking.
 
+## Recommendation validity
+
+A material owner decision derives recommendation eligibility before optimization.
+Every option assesses every governing hard invariant and references only proven or
+explicitly unproven assumptions. Any violated invariant makes the option invalid; any
+unproven invariant or referenced assumption makes it unproven. Only the complete
+derived valid set may enter cost, convenience, minimal-change, rollout, or other
+secondary ranking.
+
+High-risk recommendations require a process-created digest-bound review assignment.
+Before review, the reviewer method must match its actor kind, a non-participant host
+must attest independence, and the context is atomically reserved in the same
+project-global registry used by lifecycle review. The assigned independent
+adversarial review covers assumption evidence, invariant tracing, option
+classification, and terminal ordering.
+A missing, stale, incomplete, self-attested, context-reused, changes-requested,
+invalid, or unproven chain cannot produce a recommendation. When no valid option
+exists, the outcome is `decision-required`, not an optimized compromise. Owner
+resolution may select only a valid option and grants no lifecycle completion, merge,
+release, deployment, or adoption authority.
+
 ## Resource and generated-state policy
 
 Every operation over repository-controlled or remote input has explicit limits for

{engineering_process-0.5.0 → engineering_process-0.6.0}/README.md

@@ -57,9 +57,10 @@ distribution: the POSIX backend owns a new process session/group and the Windows
 backend owns a kill-on-close Job Object. Consumer manifests, evidence, and exit codes
 do not branch by operating system. If an outer Windows Job applies incompatible
 nesting or UI limits, target creation fails closed instead of running uncontained.
-After a command root exits, both backends allow at most 250 milliseconds for child
-accounting to drain naturally. A process still present after that bound is terminated
-and makes the command fail; commands with no remaining child return immediately.
+After a command root exits, the POSIX backend allows at most 250 milliseconds and the
+Windows Job Object backend allows at most 5 seconds for child accounting to drain
+naturally. A process still present after its platform bound is terminated and makes
+the command fail; commands with no remaining child return immediately.
 
 This task boundary intentionally separates finite commands from services and
 interactive protocols. `processctl exec`, requirement probes, setup command actions,
@@ -445,12 +446,77 @@ may authorize installing that policy but never substitutes for a missing policy.
 When new evidence exposes multiple materially valid directions or would change
 accepted scope, owner, trust boundary, authority, compatibility, rollout, or
 lifecycle order, the coordinator stops dependent mutation and asks the project owner.
-It presents evidence, the invariant, real options, trade-offs, and a recommendation;
-the accepted decision is recorded before work resumes. Bounded implementation details
+Before presenting a material recommendation, it records every hard invariant,
+assumption, and option in a bounded recommendation artifact. `processctl` derives the
+valid, invalid, and unproven sets; cost or minimal-change optimization applies only to
+the complete valid set. A distinct actor and fresh context independently challenge
+assumption evidence, invariant tracing, option classification, and terminal ordering.
+If the exact digest-bound chain is not approved or contains no valid option, the
+result is blocked rather than a recommendation. Bounded implementation details
 already decided by the contract continue autonomously.
 
+Validate the recommendation, challenge, and optional owner resolution as one chain:
+
+~~~text
+processctl contract validate --kind recommendation recommendation.json
+processctl recommendation review start --project-root . \
+  --recommendation recommendation.json \
+  --actor <reviewer> --context <fresh-context> --actor-kind agent \
+  --method isolated-context --attested-by <host> \
+  --attestation-evidence <bounded-attestation>
+processctl contract validate --kind recommendation-review-assignment \
+  .process/runs/recommendations/<decision-id>/review-request-<ids>.json
+processctl contract validate --kind recommendation-review recommendation-review.json
+processctl recommendation validate-chain --project-root . \
+  --recommendation recommendation.json \
+  --assignment .process/runs/recommendations/<decision-id>/review-request-<ids>.json \
+  --review recommendation-review.json
+processctl recommendation resolution --project-root . \
+  --recommendation recommendation.json \
+  --assignment .process/runs/recommendations/<decision-id>/review-request-<ids>.json \
+  --review recommendation-review.json \
+  --selected-option <valid-option-id> --owner-id <owner-id> \
+  --owner-evidence-sha256 sha256:<digest> \
+  --selection-rationale-sha256 sha256:<digest> \
+  --output recommendation-resolution.json
+processctl recommendation validate-chain --project-root . \
+  --recommendation recommendation.json \
+  --assignment .process/runs/recommendations/<decision-id>/review-request-<ids>.json \
+  --review recommendation-review.json \
+  --resolution recommendation-resolution.json
+~~~
+
+The review-start command reserves the context across lifecycle and recommendation
+reviews before emitting its exact assignment. Resolution creation refuses symlinked,
+existing, or concurrently created output instead of redirecting or replacing it. The
+resolution records a selected valid option but grants no lifecycle completion, merge,
+release, deployment, or adoption authority. Those owning gates remain separate. The
+accepted decision is recorded before dependent work resumes.
+
+When a schema-3 change selects a project-owned `requiredEvidence` id, local profiles
+alone do not advance it to review. Create the exact no-authority request, run the
+project adapter, and ingest the complete supplemental set first:
+
+~~~text
+processctl change remote request --project-root . --change-id issue-123 \
+  --actor worker --context worker-session --actor-kind agent
+python verification/run_remote_verification.py --project-root . \
+  --change-id issue-123 --actor worker --context worker-session \
+  --actor-kind agent --repository owner/repository \
+  --failure-output /durable/receipts/issue-123-remote-failure.json
+processctl change status --project-root . --change-id issue-123
+~~~
+
+The adapter publishes a uniquely named exact-checkpoint verification tag, never a
+branch or PR, dispatches the protected-base workflow, validates service and bundle
+digests, calls `change remote ingest`, and deletes the tag in every terminal path.
+Downloaded temporary archives are deleted after ingestion; failed evidence is moved
+to the explicit durable failure location before cleanup. Remote artifacts and their
+service ids remain lifecycle evidence, not merge, release, deployment, or adoption
+authority.
+
 The canonical publication order is stricter than a PR-first workflow: implementation
-and every required profile pass on a clean checkpoint; a consumer-selected independent
+and every required local and remote profile pass on a clean checkpoint; a consumer-selected independent
 agent or human semantically reviews that checkpoint; findings repeat implementation,
 complete verification, and fresh review until approved; `change finish` records
 completion; only then may automation push and create the PR. Static policy/secret/pin
@@ -682,7 +748,8 @@ fingerprint, source tree, or publication range.
   exclusively by their hash-locked `requirements/process.txt`. The action invokes the
   producer-owned installer from its immutable action checkout and never downloads or
   executes helper source from the consumer branch.
-- Versioned JSON schemas define change, plan, verification, review, lifecycle,
+- Versioned JSON schemas define change, plan, verification, review, recommendation,
+  independent recommendation assignment and challenge, owner resolution, lifecycle,
   completion-related artifacts, release-change fragments, and the release
   classification contract. The generated Release PR gate binds that contract to the
   exact SemVer increment, package version, latest reachable prior tag, reviewed head,

{engineering_process-0.5.0 → engineering_process-0.6.0}/VERSIONING.md

@@ -138,6 +138,31 @@ consumer reproduction after adoption. A read-only pre-release consumer candidate
 supplemental compatibility evidence only and cannot be committed as an unreleased
 dependency.
 
+## Recommendation-validity capability
+
+Recommendation, review-assignment, review, and owner-resolution schema-1 artifacts
+are additive serialized surfaces. Requiring every new material owner decision to use
+their invariant derivation, project-global fresh-context reservation, independent
+challenge, chain validation, and valid resolution changes managed workflow semantics.
+Before 1.0 this is therefore a breaking package change even though `schemaImpact`
+remains additive.
+
+After adoption, new material decisions use `recommendation review start` before the
+reviewer acts, validate the exact assignment-bound chain before presenting a
+recommendation, and record the selected valid option before dependent work resumes.
+Completed historical decisions retain their original evidence and require no
+backfill. A recommendation resolution is decision evidence only and never substitutes
+for lifecycle completion or delivery authority.
+
+Remote-verification request and evidence-set schema-1 artifacts, optional project
+requirements, optional change selections, lifecycle references, and receipt content
+are additive serialized surfaces. A project does not gain the gate until a separate
+adoption validates the target-version manifest and selects requirement ids. Once
+selected, missing exact remote evidence blocks review and completion; a later PR
+matrix is not a compatibility substitute. Provider transport remains project-owned,
+while request expansion, ingestion, invalidation, and terminal ordering are portable
+process semantics.
+
 ## Release and adoption boundary
 
 Release, self-adoption, and consumer adoption are separate changes:

{engineering_process-0.5.0 → engineering_process-0.6.0}/engineering_process/__init__.py

@@ -1,3 +1,3 @@
 """Agent-neutral engineering process."""
 
-VERSION = "0.5.0"
+VERSION = "0.6.0"

{engineering_process-0.5.0 → engineering_process-0.6.0}/engineering_process/_windows_job.py

@@ -36,7 +36,7 @@ WAIT_FAILED = 0xFFFFFFFF
 WAIT_OBJECT_0 = 0x00000000
 WAIT_TIMEOUT = 0x00000102
 CLEANUP_GRACE_MILLISECONDS = 5_000
-NATURAL_DRAIN_GRACE_MILLISECONDS = 250
+NATURAL_DRAIN_GRACE_MILLISECONDS = 5_000
 MAX_STATUS_BYTES = 4096
 MAX_STATUS_ERROR_CHARACTERS = 1024
 

{engineering_process-0.5.0 → engineering_process-0.6.0}/engineering_process/cli.py

@@ -14,6 +14,7 @@ from .bundles import load_bundles, select_bundles
 from .bootstrap import initialize_project
 from .contracts import (
     ContractError,
+    canonical_json_digest,
     derive_release_version,
     read_json,
     validate_adoption_migration,
@@ -29,6 +30,12 @@ from .contracts import (
     validate_plan,
     validate_process_lock,
     validate_project,
+    validate_recommendation,
+    validate_recommendation_resolution,
+    validate_recommendation_review,
+    validate_recommendation_review_assignment,
+    validate_remote_verification_evidence,
+    validate_remote_verification_request,
     validate_release,
     validate_release_change,
     validate_review,
@@ -70,7 +77,9 @@ from .lifecycle import (
     finish_change,
     lifecycle_environment_issues,
     lifecycle_status,
+    ingest_remote_verification,
     register_plan,
+    request_remote_verification,
     start_change,
     start_review,
     submit_review,
@@ -89,6 +98,11 @@ from .publication import (
     validate_evidence_publication,
 )
 from .process_graph import load_process_graph, process_root_from_skills
+from .recommendation import (
+    create_recommendation_resolution,
+    start_recommendation_review,
+    validate_recommendation_chain,
+)
 from .release import validate_release_checkpoint
 from .release_candidate import prepare_release_candidate, render_release_pull_request
 from .skills import validate_skills
@@ -281,6 +295,12 @@ def command_contract_validate(args: argparse.Namespace) -> int:
         "improvement-resolution": validate_improvement_resolution,
         "improvement-signal": validate_improvement_signal,
         "plan": validate_plan,
+        "recommendation": validate_recommendation,
+        "recommendation-resolution": validate_recommendation_resolution,
+        "recommendation-review": validate_recommendation_review,
+        "recommendation-review-assignment": validate_recommendation_review_assignment,
+        "remote-verification-evidence": validate_remote_verification_evidence,
+        "remote-verification-request": validate_remote_verification_request,
         "release": validate_release,
         "release-change": validate_release_change,
         "review": validate_review,
@@ -297,6 +317,56 @@ def command_contract_validate(args: argparse.Namespace) -> int:
     return 0
 
 
+def command_recommendation_validate_chain(args: argparse.Namespace) -> int:
+    _lifecycle_project(args)
+    result = validate_recommendation_chain(
+        args.project_root,
+        args.recommendation,
+        args.assignment,
+        args.review,
+        args.resolution,
+    )
+    status = "passed" if result["allowed"] else "blocked"
+    _emit(
+        args,
+        _result("recommendation validate-chain", status=status, **result),
+    )
+    return 0 if result["allowed"] else 1
+
+
+def command_recommendation_review_start(args: argparse.Namespace) -> int:
+    _lifecycle_project(args)
+    result = start_recommendation_review(
+        args.project_root,
+        args.recommendation,
+        actor_id=args.actor,
+        context_id=args.context,
+        kind=args.actor_kind,
+        method=args.method,
+        attested_by=args.attested_by,
+        evidence=args.attestation_evidence,
+    )
+    _emit(args, _result("recommendation review start", **result))
+    return 0
+
+
+def command_recommendation_resolution(args: argparse.Namespace) -> int:
+    _lifecycle_project(args)
+    result = create_recommendation_resolution(
+        args.project_root,
+        args.recommendation,
+        args.assignment,
+        args.review,
+        selected_option_id=args.selected_option,
+        owner_id=args.owner_id,
+        owner_evidence_sha256=args.owner_evidence_sha256,
+        selection_rationale_sha256=args.selection_rationale_sha256,
+        output=args.output,
+    )
+    _emit(args, _result("recommendation resolution", **result))
+    return 0
+
+
 def command_improvement_validate_chain(args: argparse.Namespace) -> int:
     result = validate_improvement_chain(
         args.signal,
@@ -600,6 +670,53 @@ def command_change_verify(args: argparse.Namespace) -> int:
     return 0
 
 
+def command_change_remote_request(args: argparse.Namespace) -> int:
+    project = _lifecycle_project(args)
+    state, request = request_remote_verification(
+        args.project_root,
+        project,
+        args.change_id,
+        actor_id=args.actor,
+        context_id=args.context,
+        kind=args.actor_kind,
+    )
+    _emit(
+        args,
+        _change_result(
+            "change remote request",
+            state,
+            checkpoint=request["checkpoint"],
+            comparisonBase=request["comparisonBase"],
+            request=state["remoteVerification"]["request"]["path"],
+            requestSha256=canonical_json_digest(request),
+        ),
+    )
+    return 0
+
+
+def command_change_remote_ingest(args: argparse.Namespace) -> int:
+    _lifecycle_project(args)
+    state, evidence = ingest_remote_verification(
+        args.project_root,
+        args.change_id,
+        args.evidence,
+        actor_id=args.actor,
+        context_id=args.context,
+        kind=args.actor_kind,
+    )
+    _emit(
+        args,
+        _change_result(
+            "change remote ingest",
+            state,
+            checkpoint=evidence["checkpoint"],
+            evidence=state["remoteVerification"]["evidence"]["path"],
+            artifactCount=len(evidence["artifacts"]),
+        ),
+    )
+    return 0
+
+
 def command_change_review_start(args: argparse.Namespace) -> int:
     _lifecycle_project(args)
     state, assignment = start_review(
@@ -673,6 +790,7 @@ def command_change_status(args: argparse.Namespace) -> int:
         plan=state["plan"],
         implementationActors=state["implementationActors"],
         verification=state["verification"],
+        remoteVerification=state.get("remoteVerification"),
         pendingFindings=state["pendingFindings"],
         reviewAssignment=state["reviewAssignment"],
         review=state["review"],
@@ -1479,6 +1597,12 @@ def build_parser() -> argparse.ArgumentParser:
             "improvement-resolution",
             "improvement-signal",
             "plan",
+            "recommendation",
+            "recommendation-resolution",
+            "recommendation-review",
+            "recommendation-review-assignment",
+            "remote-verification-evidence",
+            "remote-verification-request",
             "release",
             "release-change",
             "review",
@@ -1489,6 +1613,81 @@ def build_parser() -> argparse.ArgumentParser:
     _add_json(contract_validate)
     contract_validate.set_defaults(handler=command_contract_validate)
 
+    recommendation = commands.add_parser(
+        "recommendation",
+        help="Validate evidence-valid recommendations and owner resolutions",
+    )
+    recommendation_commands = recommendation.add_subparsers(
+        dest="recommendation_command", required=True
+    )
+    recommendation_validate = recommendation_commands.add_parser(
+        "validate-chain",
+        help="Validate recommendation validity and its independent challenge",
+    )
+    _add_project_root(recommendation_validate)
+    _add_process_root(recommendation_validate)
+    recommendation_validate.add_argument(
+        "--recommendation", type=Path, required=True
+    )
+    recommendation_validate.add_argument("--assignment", type=Path, required=True)
+    recommendation_validate.add_argument("--review", type=Path, required=True)
+    recommendation_validate.add_argument("--resolution", type=Path)
+    _add_json(recommendation_validate)
+    recommendation_validate.set_defaults(
+        handler=command_recommendation_validate_chain
+    )
+    recommendation_review = recommendation_commands.add_parser(
+        "review", help="Register an independent recommendation reviewer"
+    )
+    recommendation_review_commands = recommendation_review.add_subparsers(
+        dest="recommendation_review_command", required=True
+    )
+    recommendation_review_start = recommendation_review_commands.add_parser(
+        "start",
+        help="Reserve a fresh project-global context and create an assignment",
+    )
+    _add_project_root(recommendation_review_start)
+    _add_process_root(recommendation_review_start)
+    _add_actor(recommendation_review_start)
+    recommendation_review_start.add_argument(
+        "--recommendation", type=Path, required=True
+    )
+    recommendation_review_start.add_argument(
+        "--method", choices=("isolated-context", "separate-person"), required=True
+    )
+    recommendation_review_start.add_argument("--attested-by", required=True)
+    recommendation_review_start.add_argument(
+        "--attestation-evidence", required=True
+    )
+    _add_json(recommendation_review_start)
+    recommendation_review_start.set_defaults(
+        handler=command_recommendation_review_start
+    )
+    recommendation_resolution = recommendation_commands.add_parser(
+        "resolution",
+        help="Create a non-authorizing owner resolution for an approved chain",
+    )
+    _add_project_root(recommendation_resolution)
+    _add_process_root(recommendation_resolution)
+    recommendation_resolution.add_argument(
+        "--recommendation", type=Path, required=True
+    )
+    recommendation_resolution.add_argument("--assignment", type=Path, required=True)
+    recommendation_resolution.add_argument("--review", type=Path, required=True)
+    recommendation_resolution.add_argument("--selected-option", required=True)
+    recommendation_resolution.add_argument("--owner-id", required=True)
+    recommendation_resolution.add_argument(
+        "--owner-evidence-sha256", required=True
+    )
+    recommendation_resolution.add_argument(
+        "--selection-rationale-sha256", required=True
+    )
+    recommendation_resolution.add_argument("--output", type=Path, required=True)
+    _add_json(recommendation_resolution)
+    recommendation_resolution.set_defaults(
+        handler=command_recommendation_resolution
+    )
+
     skills = commands.add_parser("skills", help="Validate portable Agent Skills")
     skills_commands = skills.add_subparsers(dest="skills_command", required=True)
     skills_validate = skills_commands.add_parser("validate")
@@ -2179,6 +2378,29 @@ def build_parser() -> argparse.ArgumentParser:
     change_verify.add_argument("--profile", required=True)
     change_verify.set_defaults(handler=command_change_verify)
 
+    change_remote = change_commands.add_parser(
+        "remote", help="Bind required exact-checkpoint remote verification"
+    )
+    remote_commands = change_remote.add_subparsers(
+        dest="change_remote_command", required=True
+    )
+    remote_request = remote_commands.add_parser(
+        "request", help="Create an exact no-authority remote verification request"
+    )
+    _add_lifecycle_common(remote_request)
+    _add_actor(remote_request)
+    remote_request.add_argument("--change-id", required=True)
+    remote_request.set_defaults(handler=command_change_remote_request)
+
+    remote_ingest = remote_commands.add_parser(
+        "ingest", help="Validate and bind a complete remote evidence set"
+    )
+    _add_lifecycle_common(remote_ingest)
+    _add_actor(remote_ingest)
+    remote_ingest.add_argument("--change-id", required=True)
+    remote_ingest.add_argument("--evidence", type=Path, required=True)
+    remote_ingest.set_defaults(handler=command_change_remote_ingest)
+
     change_review = change_commands.add_parser(
         "review", help="Run the independent-review gate"
     )

{engineering_process-0.5.0 → engineering_process-0.6.0}/engineering_process/command_catalog.py

@@ -8,6 +8,8 @@ LIFECYCLE_COMMAND_PATHS = frozenset(
         "change finish",
         "change implement",
         "change plan",
+        "change remote ingest",
+        "change remote request",
         "change review start",
         "change review submit",
         "change start",