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

I0907

The running process says what it is, from an allowlist

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
ACTIVE
Wave
2
Waiting on
none
Holds back
none
Behind it in all
0
Evidence
0 of 3
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 I0907

majordomus plan verify I0907

majordomus plan done I0907

What it is

Objective
Expose the version, revision, build profile, target and the safe platform facts of a hosted process through the existing metadata surface, with every field explicitly allowlisted.
Why
Verifying that the deployed image is the one that was built requires the running process to say which revision it is. Doing that by reflecting the environment would publish whatever the platform happens to inject, including things that must never leave the Machine.
Now
about.rs carries the executable's own description. Nothing reports the build revision or any platform fact, because nothing is deployed.
Wanted
One metadata read reports an allowlisted set of build and platform fields, and a test proves that a value outside the allowlist cannot reach it.
Done when
unknown: the record declares no `completion`
Risk
A build timestamp defeats reproducibility. It is included only if the reproducibility decision in I0910 permits it.

Acceptance

  • Version, commit revision, build profile and target are embedded at build time through the existing version infrastructure
  • Platform facts are read from the hosting environment by explicit name only, and absence is reported as absence rather than as an error
  • A test proves an environment variable outside the allowlist never appears in the output, including one whose name resembles a secret
  • The metadata read is a registered capability and appears in OpenAPI and the reference without a second registration
Validation
cargo test --workspace --all-featuresmajordomus generate --check
Evidence required
metadata_allowlistedfly_platform_fieldsredaction_test
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
apps/majordomus-cli/src/about.rsapps/majordomus-cli/build.rs
Not
Any environment dump, any pass-through of unknown variablesAny credential, token or authorization header, in any form
Depends on
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-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.