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

I0829

Performance doctrine as project rules

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
Behind it in all
2
Evidence
1 of 1
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 I0829

majordomus plan verify I0829

majordomus plan done I0829

What it is

Objective
Add project rules: derived state is computed once per state version, a command's hot path does not re-parse canonical files, every public command is benchmarkable from the registry, cacheability never changes observable behaviour, and performance claims need benchmark evidence.
Why
A rule that lives only in a document is not enforced; project rules are loaded by every worker and named by doctor.
Now
No performance rule exists.
Wanted
Five rules under .ai/repo/rules/project, advisory where a reviewer decides and enforced by the cases and counters where a case exists, each naming its case.
Done when
unknown: the record declares no `completion`
Risk
project.no-new-nouns: the rules use the existing vocabulary (phase, counter, cache, baseline) and add no concept.

Acceptance

  • rules list shows the five rules resolving
  • Each rule names the case or the review that proves it
Validation
bin/majordomus rules listbash test/run.sh 67_rule_dag
Evidence required
docs_integrated
Evidence present
docs_integrated

Scope

Touches
.ai/repo/rules/projectdocs/DOCTRINE.md
Not
Provider-specific copies
Depends on
none
Priority
p0
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-05
Updated
2026-09-05
Started
2026-09-05T03:47:33Z
Verified
2026-09-05T03:47:33Z
Completed
2026-09-05T03:47:33Z

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.