Skip to content
Cockpit0.29.0
A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:06:01Z by majordomus 0.29.0. Nothing on this page is read again. See it live

I0204

Apply one derived limit for real and prove it changes what happens

Where it stands

devtask.issue
Readiness
blocked 1 of its dependencies is not DONE
Status
BLOCKED
Can start
not now
Milestone
runtime-adapters
Milestone status
PLANNED
Wave
3
Waiting on
I0203
Holds back
I0205
Behind it in all
2
Evidence
0 of 2
In the waySubjectDetail
issueI0203I0203 is not DONE

Moves

plan.transition
A move writes the repository: it stamps one field of this issue's record and appends one event to the ledger, and a commit will carry both.
The same moves from a terminal

majordomus plan start I0204

majordomus plan verify I0204

majordomus plan done I0204

What it is

Objective
Implement the first adapter: one limit, derived from the profile through the resolver, applied where a provider can honestly apply it, with a behavioural case that fails if the limit stops being applied.
Why
The milestone's whole distinction is between a limit that is printed and a limit that is applied. One limit that genuinely bites is worth more than a full set that is advisory, and it is the only thing that makes the claim publishable.
Now
The mapping exists, the resolver prints the numbers, and the opt-in exists. Nothing anywhere applies a value to anything.
Wanted
With enforcement on, one provider's execution is constrained by a value derived from the active profile, and turning the profile from one value to another changes the observed outcome.
Done when
unknown: the record declares no `completion`
Risk
The only honest adapters are for knobs a provider exposes and documents; if the chosen knob turns out to be advisory on the provider's side, the issue closes as no_match rather than shipping a clamp that does not clamp.

Acceptance

  • The applied value comes from the resolver, and no constant appears in the adapter
  • A case changes only the profile and observes a different outcome
  • A case with enforcement off observes the unconstrained outcome
  • Removing the application makes a case fail rather than a document go stale
Validation
bash test/run.sh
Evidence required
suiteprofile_changes_outcome
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
libsharetest/cases
Not
A second provider; one honest adapter firstAny provider knob whose effect cannot be observed from a test in this repository
Depends on
I0203
Priority
p1
Profile
debugging
Parallel safe
false
Owner
unknown: the record declares no `owner`

The work so far

Branches
none
Merged
none
Commits
0
Trunk
master
Sessions
none
Created
2026-09-04
Updated
2026-09-04
Started
unknown: the record declares no `started_at`
Verified
unknown: the record declares no `verified_at`
Completed
unknown: the record declares no `completed_at`

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.