A snapshot: read at commit dd4c0a87cba on 2026-10-19T09:32:43Z by majordomus 0.30.2. Nothing on this page is read again. See it live
I1803
New shell is refused without a declared exemption, and the migration inventory is tracked
Where it stands
devtask.issue- Readiness
- complete completion is recorded and every required evidence token is present
- Status
- DONE
- Can start
- not now
- Milestone
- Milestone status
- ACTIVE
- Wave
0- Waiting on
- none
- Holds back
- none
- Behind it in all
0- Evidence
1of1
Moves
plan.transitionWhat it is
- Objective
- Refuse a new shell file under a governed path unless a machine-readable exemption list names it, and track the inventory of existing shell with each unit's disposition.
- Why
- Migration shrinks shell only if nothing grows it back. The audit of 2026-09-15 classified 223 units (scripts/ci 44 files and 6,017 lines; other scripts and bin 82 files and 14,860 lines; lib 45 files and 19,513 lines; 216 shell cases and 30,872 lines): 97 core Rust, 32 orchestration, 34 glue, 3 dead, 14 generated, 43 platform adaptor. Worked on branch feature/new-shell-is-refused.
- Now
- Nothing refuses a new shell file; the inventory exists only as an audit report.
- Wanted
- A gate and an exemption list; the inventory is a tracked, machine-readable record each migration updates.
- Done when
- unknown: the record declares no `completion`
- Risk
- unknown: the record declares no `risk`
Acceptance
- a new shell file under a governed path without an exemption fails the gate
- every existing shell unit appears in the inventory with its disposition
- Validation
bash test/run.sh- Evidence required
new_shell_refused- Evidence present
new_shell_refused
Scope
- Touches
scripts.ai/repotest- Not
Migrating any unit- Depends on
- none
- Priority
- p1
- Profile
- implementation
- Parallel safe
- true
- Owner
- unknown: the record declares no `owner`
The work so far
- Branches
- none
- Merged
- none
- Commits
0- Trunk
- master
- Sessions
- none
- Created
- 2026-09-15
- Updated
- 2026-10-14T21:36:57Z
- Started
- 2026-10-14T21:36:29Z
- Verified
- unknown: the record declares no `verified_at`
- Completed
- 2026-10-14T21:36:57Z
Synchronisation
- Adapter
scripts/github-sync- Repository
- unknown: the derived plan's header carries no repository
- External issue
- unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
- State there
- unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
Findings
Nothing is wrong with these records.