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

I1103

Whether a file is authored or derived is a field, not a naming convention

Where it stands

devtask.issue
Readiness
blocked 1 of its dependencies is not DONE
Status
BLOCKED
Can start
not now
Milestone
two-folder-integration
Milestone status
ACTIVE
Wave
2
Waiting on
I1102
Holds back
none
Behind it in all
0
Evidence
0 of 2
In the waySubjectDetail
issueI1102I1102 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 I1103

majordomus plan verify I1103

majordomus plan done I1103

What it is

Objective
Give every machine-processable artifact an explicit provenance and lifecycle — authored, derived, generated, cache or runtime — with its generator, its inputs and whether it is disposable, so that no consumer has to infer from a path what a file is.
Why
A generated file that is indistinguishable from an authored one eventually becomes an input, and then it cannot be regenerated without losing something. Deciding that by directory name works until the first exception.
Now
Generated artifacts carry a banner or an extension member saying they are generated, which the manifest validator reads. Nothing states a generator's inputs or whether an artifact may be deleted and rebuilt.
Wanted
Provenance and lifecycle are typed fields every artifact carries, and a consumer decides what it may do with a file by reading them.
Done when
unknown: the record declares no `completion`
Risk
Recording inputs invites recording them by hand. The input list is derived from the generator, or it is not recorded.

Acceptance

  • Every generated artifact declares its generator, its version and the canonical inputs it derives from
  • Disposability is explicit, so a consumer can tell what may be deleted and rebuilt from what may not
  • A generated artifact is never read back as canonical input, and a check proves it
  • Authored artifacts are distinguishable from derived ones without consulting a path
Validation
majordomus generate --checkcargo test --workspace --all-features
Evidence required
provenance_declareddisposability_explicit
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
apps/majordomus-cli/src/generate.rsshare/schemas
Not
Replacing the existing banner mechanism where it already answers the questionA provenance field that repeats what the schema id already fixes
Depends on
I1102
Priority
p0
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-06
Updated
2026-09-06
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.