Preserve repository authority across recovery

.agents/skills/boatstack-autoplan/SKILL.md

@@ -14,14 +14,32 @@ Bind one command-scoped context containing the exact goal, delivery, repository,
 worktree, flow, actor, and supplied authority receipts. Preserve that context
 through every `next`, `apply`, `recover`, and re-resolution. Never synthesize missing
 authority or infer it from authentication, files, branches, or prior conversation.
+Within that context, track requested authority sources separately from currently
+materialized authority receipts.
+
+For this operation, request human and repository-policy authority sources. The
+repository-policy source remains requested when configuration is
+stale, uninitialized, or under recovery; do not pass `--repository-authority`
+until the current configuration has exact verified fingerprint evidence.
+
+After a complete `installation.initialize`, `configuration.initialize`, or recovery
+receipt, re-observe the post-receipt state. If configuration is now verified,
+make one bounded attempt for that receipt to materialize the retained source by
+adding `--repository-authority` to the next resolution. The kernel must derive the
+receipt from that exact verified fingerprint. Never derive repository authority
+from file presence, authentication, or prior conversation. If the source remains
+unverifiable, record it as conclusively rejected and fail closed; do not retry it
+again for the same receipt.
 
 Begin each cycle with an untargeted authority-bearing `next`. Apply only the
 stable transition ID from the immediately preceding prescription and only its
 declared parameters. Preserve the complete apply response and stderr, including
 admission, receipt, postcondition, error, recovery, and transaction fields.
 Re-resolve with the same context after every complete receipt.
 
-Stop only on an authority-bearing `FRONTIER`, `BLOCKED`, `REFUSED`, or
+Evaluate a frontier only after every requested authority source is materialized
+or conclusively rejected against the post-receipt state. Stop only on an
+authority-bearing `FRONTIER`, `BLOCKED`, `REFUSED`, or
 `UNRESOLVED` result for this operation. Treat `TERMINAL` as exact goal evidence.
 If recovery is active, use only a transition in `recovery_info.permitted` and
 the exact transaction ID. Never choose maintenance, correction, abandonment,

.agents/skills/boatstack-run/SKILL.md

@@ -14,14 +14,32 @@ Bind one command-scoped context containing the exact goal, delivery, repository,
 worktree, flow, actor, and supplied authority receipts. Preserve that context
 through every `next`, `apply`, `recover`, and re-resolution. Never synthesize missing
 authority or infer it from authentication, files, branches, or prior conversation.
+Within that context, track requested authority sources separately from currently
+materialized authority receipts.
+
+For this operation, request human and repository-policy authority sources. The
+repository-policy source remains requested when configuration is
+stale, uninitialized, or under recovery; do not pass `--repository-authority`
+until the current configuration has exact verified fingerprint evidence.
+
+After a complete `installation.initialize`, `configuration.initialize`, or recovery
+receipt, re-observe the post-receipt state. If configuration is now verified,
+make one bounded attempt for that receipt to materialize the retained source by
+adding `--repository-authority` to the next resolution. The kernel must derive the
+receipt from that exact verified fingerprint. Never derive repository authority
+from file presence, authentication, or prior conversation. If the source remains
+unverifiable, record it as conclusively rejected and fail closed; do not retry it
+again for the same receipt.
 
 Begin each cycle with an untargeted authority-bearing `next`. Apply only the
 stable transition ID from the immediately preceding prescription and only its
 declared parameters. Preserve the complete apply response and stderr, including
 admission, receipt, postcondition, error, recovery, and transaction fields.
 Re-resolve with the same context after every complete receipt.
 
-Stop only on an authority-bearing `FRONTIER`, `BLOCKED`, `REFUSED`, or
+Evaluate a frontier only after every requested authority source is materialized
+or conclusively rejected against the post-receipt state. Stop only on an
+authority-bearing `FRONTIER`, `BLOCKED`, `REFUSED`, or
 `UNRESOLVED` result for this operation. Treat `TERMINAL` as exact goal evidence.
 If recovery is active, use only a transition in `recovery_info.permitted` and
 the exact transaction ID. Never choose maintenance, correction, abandonment,

.agents/skills/boatstack-update/SKILL.md

@@ -14,14 +14,22 @@ Bind one command-scoped context containing the exact goal, delivery, repository,
 worktree, flow, actor, and supplied authority receipts. Preserve that context
 through every `next`, `apply`, `recover`, and re-resolution. Never synthesize missing
 authority or infer it from authentication, files, branches, or prior conversation.
+Within that context, track requested authority sources separately from currently
+materialized authority receipts.
+
+For this operation, request only checksum-verified installation authority. Do not
+request or materialize repository, provider, publication, product-delivery, or
+merge authority. Installation receipts cannot be reused to broaden this scope.
 
 Begin each cycle with an untargeted authority-bearing `next`. Apply only the
 stable transition ID from the immediately preceding prescription and only its
 declared parameters. Preserve the complete apply response and stderr, including
 admission, receipt, postcondition, error, recovery, and transaction fields.
 Re-resolve with the same context after every complete receipt.
 
-Stop only on an authority-bearing `FRONTIER`, `BLOCKED`, `REFUSED`, or
+Evaluate a frontier only after every requested authority source is materialized
+or conclusively rejected against the post-receipt state. Stop only on an
+authority-bearing `FRONTIER`, `BLOCKED`, `REFUSED`, or
 `UNRESOLVED` result for this operation. Treat `TERMINAL` as exact goal evidence.
 If recovery is active, use only a transition in `recovery_info.permitted` and
 the exact transaction ID. Never choose maintenance, correction, abandonment,

.claude/skills/boatstack-autoplan/SKILL.md

@@ -14,14 +14,32 @@ Bind one command-scoped context containing the exact goal, delivery, repository,
 worktree, flow, actor, and supplied authority receipts. Preserve that context
 through every `next`, `apply`, `recover`, and re-resolution. Never synthesize missing
 authority or infer it from authentication, files, branches, or prior conversation.
+Within that context, track requested authority sources separately from currently
+materialized authority receipts.
+
+For this operation, request human and repository-policy authority sources. The
+repository-policy source remains requested when configuration is
+stale, uninitialized, or under recovery; do not pass `--repository-authority`
+until the current configuration has exact verified fingerprint evidence.
+
+After a complete `installation.initialize`, `configuration.initialize`, or recovery
+receipt, re-observe the post-receipt state. If configuration is now verified,
+make one bounded attempt for that receipt to materialize the retained source by
+adding `--repository-authority` to the next resolution. The kernel must derive the
+receipt from that exact verified fingerprint. Never derive repository authority
+from file presence, authentication, or prior conversation. If the source remains
+unverifiable, record it as conclusively rejected and fail closed; do not retry it
+again for the same receipt.
 
 Begin each cycle with an untargeted authority-bearing `next`. Apply only the
 stable transition ID from the immediately preceding prescription and only its
 declared parameters. Preserve the complete apply response and stderr, including
 admission, receipt, postcondition, error, recovery, and transaction fields.
 Re-resolve with the same context after every complete receipt.
 
-Stop only on an authority-bearing `FRONTIER`, `BLOCKED`, `REFUSED`, or
+Evaluate a frontier only after every requested authority source is materialized
+or conclusively rejected against the post-receipt state. Stop only on an
+authority-bearing `FRONTIER`, `BLOCKED`, `REFUSED`, or
 `UNRESOLVED` result for this operation. Treat `TERMINAL` as exact goal evidence.
 If recovery is active, use only a transition in `recovery_info.permitted` and
 the exact transaction ID. Never choose maintenance, correction, abandonment,

.claude/skills/boatstack-run/SKILL.md

@@ -14,14 +14,32 @@ Bind one command-scoped context containing the exact goal, delivery, repository,
 worktree, flow, actor, and supplied authority receipts. Preserve that context
 through every `next`, `apply`, `recover`, and re-resolution. Never synthesize missing
 authority or infer it from authentication, files, branches, or prior conversation.
+Within that context, track requested authority sources separately from currently
+materialized authority receipts.
+
+For this operation, request human and repository-policy authority sources. The
+repository-policy source remains requested when configuration is
+stale, uninitialized, or under recovery; do not pass `--repository-authority`
+until the current configuration has exact verified fingerprint evidence.
+
+After a complete `installation.initialize`, `configuration.initialize`, or recovery
+receipt, re-observe the post-receipt state. If configuration is now verified,
+make one bounded attempt for that receipt to materialize the retained source by
+adding `--repository-authority` to the next resolution. The kernel must derive the
+receipt from that exact verified fingerprint. Never derive repository authority
+from file presence, authentication, or prior conversation. If the source remains
+unverifiable, record it as conclusively rejected and fail closed; do not retry it
+again for the same receipt.
 
 Begin each cycle with an untargeted authority-bearing `next`. Apply only the
 stable transition ID from the immediately preceding prescription and only its
 declared parameters. Preserve the complete apply response and stderr, including
 admission, receipt, postcondition, error, recovery, and transaction fields.
 Re-resolve with the same context after every complete receipt.
 
-Stop only on an authority-bearing `FRONTIER`, `BLOCKED`, `REFUSED`, or
+Evaluate a frontier only after every requested authority source is materialized
+or conclusively rejected against the post-receipt state. Stop only on an
+authority-bearing `FRONTIER`, `BLOCKED`, `REFUSED`, or
 `UNRESOLVED` result for this operation. Treat `TERMINAL` as exact goal evidence.
 If recovery is active, use only a transition in `recovery_info.permitted` and
 the exact transaction ID. Never choose maintenance, correction, abandonment,

.claude/skills/boatstack-update/SKILL.md

@@ -14,14 +14,22 @@ Bind one command-scoped context containing the exact goal, delivery, repository,
 worktree, flow, actor, and supplied authority receipts. Preserve that context
 through every `next`, `apply`, `recover`, and re-resolution. Never synthesize missing
 authority or infer it from authentication, files, branches, or prior conversation.
+Within that context, track requested authority sources separately from currently
+materialized authority receipts.
+
+For this operation, request only checksum-verified installation authority. Do not
+request or materialize repository, provider, publication, product-delivery, or
+merge authority. Installation receipts cannot be reused to broaden this scope.
 
 Begin each cycle with an untargeted authority-bearing `next`. Apply only the
 stable transition ID from the immediately preceding prescription and only its
 declared parameters. Preserve the complete apply response and stderr, including
 admission, receipt, postcondition, error, recovery, and transaction fields.
 Re-resolve with the same context after every complete receipt.
 
-Stop only on an authority-bearing `FRONTIER`, `BLOCKED`, `REFUSED`, or
+Evaluate a frontier only after every requested authority source is materialized
+or conclusively rejected against the post-receipt state. Stop only on an
+authority-bearing `FRONTIER`, `BLOCKED`, `REFUSED`, or
 `UNRESOLVED` result for this operation. Treat `TERMINAL` as exact goal evidence.
 If recovery is active, use only a transition in `recovery_info.permitted` and
 the exact transaction ID. Never choose maintenance, correction, abandonment,

.cursor/commands/boatstack-autoplan.md

@@ -14,14 +14,32 @@ Bind one command-scoped context containing the exact goal, delivery, repository,
 worktree, flow, actor, and supplied authority receipts. Preserve that context
 through every `next`, `apply`, `recover`, and re-resolution. Never synthesize missing
 authority or infer it from authentication, files, branches, or prior conversation.
+Within that context, track requested authority sources separately from currently
+materialized authority receipts.
+
+For this operation, request human and repository-policy authority sources. The
+repository-policy source remains requested when configuration is
+stale, uninitialized, or under recovery; do not pass `--repository-authority`
+until the current configuration has exact verified fingerprint evidence.
+
+After a complete `installation.initialize`, `configuration.initialize`, or recovery
+receipt, re-observe the post-receipt state. If configuration is now verified,
+make one bounded attempt for that receipt to materialize the retained source by
+adding `--repository-authority` to the next resolution. The kernel must derive the
+receipt from that exact verified fingerprint. Never derive repository authority
+from file presence, authentication, or prior conversation. If the source remains
+unverifiable, record it as conclusively rejected and fail closed; do not retry it
+again for the same receipt.
 
 Begin each cycle with an untargeted authority-bearing `next`. Apply only the
 stable transition ID from the immediately preceding prescription and only its
 declared parameters. Preserve the complete apply response and stderr, including
 admission, receipt, postcondition, error, recovery, and transaction fields.
 Re-resolve with the same context after every complete receipt.
 
-Stop only on an authority-bearing `FRONTIER`, `BLOCKED`, `REFUSED`, or
+Evaluate a frontier only after every requested authority source is materialized
+or conclusively rejected against the post-receipt state. Stop only on an
+authority-bearing `FRONTIER`, `BLOCKED`, `REFUSED`, or
 `UNRESOLVED` result for this operation. Treat `TERMINAL` as exact goal evidence.
 If recovery is active, use only a transition in `recovery_info.permitted` and
 the exact transaction ID. Never choose maintenance, correction, abandonment,

.cursor/commands/boatstack-run.md

@@ -14,14 +14,32 @@ Bind one command-scoped context containing the exact goal, delivery, repository,
 worktree, flow, actor, and supplied authority receipts. Preserve that context
 through every `next`, `apply`, `recover`, and re-resolution. Never synthesize missing
 authority or infer it from authentication, files, branches, or prior conversation.
+Within that context, track requested authority sources separately from currently
+materialized authority receipts.
+
+For this operation, request human and repository-policy authority sources. The
+repository-policy source remains requested when configuration is
+stale, uninitialized, or under recovery; do not pass `--repository-authority`
+until the current configuration has exact verified fingerprint evidence.
+
+After a complete `installation.initialize`, `configuration.initialize`, or recovery
+receipt, re-observe the post-receipt state. If configuration is now verified,
+make one bounded attempt for that receipt to materialize the retained source by
+adding `--repository-authority` to the next resolution. The kernel must derive the
+receipt from that exact verified fingerprint. Never derive repository authority
+from file presence, authentication, or prior conversation. If the source remains
+unverifiable, record it as conclusively rejected and fail closed; do not retry it
+again for the same receipt.
 
 Begin each cycle with an untargeted authority-bearing `next`. Apply only the
 stable transition ID from the immediately preceding prescription and only its
 declared parameters. Preserve the complete apply response and stderr, including
 admission, receipt, postcondition, error, recovery, and transaction fields.
 Re-resolve with the same context after every complete receipt.
 
-Stop only on an authority-bearing `FRONTIER`, `BLOCKED`, `REFUSED`, or
+Evaluate a frontier only after every requested authority source is materialized
+or conclusively rejected against the post-receipt state. Stop only on an
+authority-bearing `FRONTIER`, `BLOCKED`, `REFUSED`, or
 `UNRESOLVED` result for this operation. Treat `TERMINAL` as exact goal evidence.
 If recovery is active, use only a transition in `recovery_info.permitted` and
 the exact transaction ID. Never choose maintenance, correction, abandonment,

.cursor/commands/boatstack-update.md

@@ -14,14 +14,22 @@ Bind one command-scoped context containing the exact goal, delivery, repository,
 worktree, flow, actor, and supplied authority receipts. Preserve that context
 through every `next`, `apply`, `recover`, and re-resolution. Never synthesize missing
 authority or infer it from authentication, files, branches, or prior conversation.
+Within that context, track requested authority sources separately from currently
+materialized authority receipts.
+
+For this operation, request only checksum-verified installation authority. Do not
+request or materialize repository, provider, publication, product-delivery, or
+merge authority. Installation receipts cannot be reused to broaden this scope.
 
 Begin each cycle with an untargeted authority-bearing `next`. Apply only the
 stable transition ID from the immediately preceding prescription and only its
 declared parameters. Preserve the complete apply response and stderr, including
 admission, receipt, postcondition, error, recovery, and transaction fields.
 Re-resolve with the same context after every complete receipt.
 
-Stop only on an authority-bearing `FRONTIER`, `BLOCKED`, `REFUSED`, or
+Evaluate a frontier only after every requested authority source is materialized
+or conclusively rejected against the post-receipt state. Stop only on an
+authority-bearing `FRONTIER`, `BLOCKED`, `REFUSED`, or
 `UNRESOLVED` result for this operation. Treat `TERMINAL` as exact goal evidence.
 If recovery is active, use only a transition in `recovery_info.permitted` and
 the exact transaction ID. Never choose maintenance, correction, abandonment,