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

I2001

start asks what the task serves and refuses a refused binding where the policy requires it

Where it stands

In the way	Subject	Detail
issue	`I2000`	I2000 is not DONE
milestone	`intent-bound-work`	the milestone intent-bound-work waits on an outcome of its own

Objective: Give start the flags --issue, --intent, --exempt and --because; ask intents.binding through the built executable; under policy intent.binding: required refuse a refused or unreadable binding, under advisory report it, and when the key is absent change nothing. Record what was named and the revision in the task record and the task.started ledger event.
Why: Until start asks, the binding is a query nobody is obliged to make and work on an uncritiqued intent begins unrefused.
Now: start takes a description, a scope, requires, a profile and an owner, and reads no intent.
Wanted: A task record carries issue, intent or exemption with its reason, and binding_revision; a refused binding is refused (exit 15) naming the cause and the three ways through.
Done when: unknown: the record declares no `completion`
Risk: unknown: the record declares no `risk`

Under required, start with a refused binding is refused (exit 15) and writes no task record
Under required, start with --exempt of a declared class and --because starts and the ledger carries both
With the policy key absent, start with no new flag behaves exactly as before
continuity.state reports what the active task named
The policy schema, the task record schema and the task.started event declare the new keys, and doctor passes with the policy key set
intent realization reads the issue a task named from the ledger as a declared link, and agrees with intents.binding about the same task
A scope that lies outside the named issue's scope is said in the binding as a note the start prints
Under required an unreadable binding (no built executable, no jq) refuses naming the command that builds it; under advisory it warns; with the key absent a flag that was given is still asked and an unreadable answer refuses
The share of scope-only starts that bind against this repository's plan is measured before this repository's policy is set to required, and the value chosen is recorded with the measurement

Validation: bash test/run.sh 960_a_task_starts_bound_to_what_it_servesbash test/run.sh 04_start_check
Evidence required: start_refuses_a_refused_bindingan_absent_policy_key_changes_nothingrealization_and_binding_agreescope_only_binding_rate_measured
Evidence present: unknown: the record carries no `evidence` entries

Touches: lib/start.shlib/intent_binding.sh.ai/repo/policy.yamlapps/majordomus-cli/src/capability/builtin/continuity.rstest/cases/960_a_task_starts_bound_to_what_it_serves.shdocslib/common.shshare/schemas/majordomus/policyshare/schemas/majordomus/currentshare/skeletonshare/events.yamlshare/allowapps/majordomus-cli/src/intent_realization.rsapps/majordomus-cli/tests/intent_realization.rs
Not: unknown: the record declares no `non_scope`
Depends on: I2000
Priority: p1
Profile: implementation
Parallel safe: false
Owner: unknown: the record declares no `owner`

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

Nothing is wrong with these records.