Enforce accepted package authority at runtime #71
Notifications
Due Date
No due date set.
Blocks
Reference: sam/archie#71
Reference in new issue
Block a user
Goal
A package step attempting a forge action, trigger or tool outside its accepted authority fails.
Evidence
store.md 'Nothing a package does at runtime can exceed its accepted authority'; AcceptedAuthority is consulted only in infrastructure/secretengine/runner.go:104. Tracked loosely as em7s.3: close that with this.
Rules
Read CLAUDE.md. Do only what the Goal and Stop when need. File anything else you notice as a bead; do not fix it. Run
task checkonce at the end; if it fails twice on the same problem, comment on this bead and stop.Stop when
Then commit (Conventional Commits, scoped by package),
bd closethis bead and stop.Close reason
Forge permissions enforced for package workflows. Tools, trigger and pin-replacement filed as follow-ups.
Imported from beads
archie-core-4q28.19· GitHub #1244 · type feature · priority P1 · created 2026-10-05 · closed 2026-10-10sam wrote (originally 2026-10-08):
Investigation: workflow projection preserves only ID/YAML, task grants preserve only task ID/expiry, and task-scoped Update can replace workflow pins. Runtime checks need authoritative package provenance retained through projection and snapshotted by the State Store when issuing the run grant; deriving authority from worker fields or current contribution ownership can allow widening after edits/removal. No partial security fix committed.