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

I1900

An intent is a typed record whose stage and satisfaction are derived

Where it stands

devtask.issue
Readiness
ready no dependency and no gate holds it; nobody has started it
Status
READY
Can start
startable
Milestone
Milestone status
PLANNED
Wave
0
Waiting on
none
Holds back
Behind it in all
3
Evidence
0 of 2
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 I1900

majordomus plan verify I1900

majordomus plan done I1900

What it is

Objective
Deliver slice 1 of the intent-lifecycle milestone: the intent kind and schema, the read-only capabilities intent.list, intent.record, intent.validate and intent.preflight on every surface, and the intent-check gate.
Why
Nothing above a milestone recorded what must become true, so no command could say which outcome a change serves or whether finished milestones achieved it (ADR 0070).
Now
No intent kind, capability or gate exists on master.
Wanted
An intent's stage follows the plan and its satisfaction follows recorded evidence, answered identically on the command line, HTTP and MCP, and an invalid intent model fails a gate.
Done when
unknown: the record declares no `completion`
Risk
unknown: the record declares no `risk`

Acceptance

  • The stage of an intent follows the derived milestone status and satisfaction follows only recorded evidence
  • The command line, HTTP and MCP answer the same derived intents
  • intent validate exits 10 naming the finding on an invalid model, and the intent-check gate runs it
Validation
majordomus intent validatecargo test --test intentbash test/run.sh 367_an_intent_is_satisfied_only_by_evidence
Evidence required
intent_stage_is_derivedintent_surfaces_agree
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
apps/majordomus-cli/src/intent.rsapps/majordomus-cli/src/capability/builtin/intents.rsshare/schemas/majordomus/intent.ai/repo/project/intents.ai/repo/ci/gates.yaml
Not
unknown: the record declares no `non_scope`
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-09-15
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

LevelCodeMessageReproduce
WARNscope_conflictshares share/schemas/majordomus/intent with I1980; they may not run concurrentlymajordomus plan validate
WARNscope_conflictshares apps/majordomus-cli/src/intent.rs with I1999; they may not run concurrentlymajordomus plan validate
WARNscope_conflictshares .ai/repo/ci/gates.yaml with I2662; they may not run concurrentlymajordomus plan validate
WARNscope_conflictshares .ai/repo/ci/gates.yaml with I2716; they may not run concurrentlymajordomus plan validate
WARNscope_conflictshares apps/majordomus-cli/src/capability/builtin/intents.rs with I2720; they may not run concurrentlymajordomus plan validate
WARNscope_conflictshares share/schemas/majordomus/intent with I2742; they may not run concurrentlymajordomus plan validate