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

I0202

Resolve a task's effective limits and print them as data

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
1
Waiting on
I0201
Holds back
I0203
Behind it in all
4
Evidence
0 of 1
In the waySubjectDetail
issueI0201I0201 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 I0202

majordomus plan verify I0202

majordomus plan done I0202

What it is

Objective
Add a read-only command that resolves the limits the active task's profile derives and prints them, in text and as JSON, so that a worker, a wrapper or a test can read the same numbers the enforcement will use.
Why
A limit that cannot be read before it bites is a limit nobody can test, and a limit computed twice is a limit that will disagree with itself. One resolver, one output, consumed by everything downstream.
Now
The mapping declares what a limit is. Nothing computes the limits for a given task, and the task record carries no way to ask.
Wanted
Running one command inside a task prints every limit the profile derives and the axis each came from. With no active task it resolves the default profile and says so.
Done when
unknown: the record declares no `completion`
Risk
A second computation of a limit anywhere else silently forks the contract; the case has to compare the enforced value against this command's output rather than against a constant.

Acceptance

  • The command prints every declared limit, its value, and the profile axis it was derived from
  • JSON output carries the same set the text output does
  • With no active task the default profile is resolved and named as the default
  • The resolver is the only place a limit value is computed
Validation
bash test/run.sh
Evidence required
suite
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
libbin
Not
Enforcing any limitCaching the resolved values anywhere; resolution is cheap and stays derived
Depends on
I0201
Priority
p1
Profile
implementation
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.