I3363 — One admitted foreign repository is adopted from the published installer to an accepted finish by a real coding agent, and its record is committed whatever its outcome

✕BLOCKED wave 4 · p0 · implementation profile · parallel safe

Part of a-foreign-repository-is-adopted-and-measured — A repository not built around Majordomus is adopted from the published installer to an accepted finish, and its overhead and friction are recorded without exposing what its basis does not permit.

Objective

In a local clone of an admitted candidate at its adopted commit, follow the workflow literally from the published installer: init, update, capture install, a first task by a real coding agent under majordomus start with a narrow scope, the first refusal, the accepted finish after the repository's own verify command passes, and removal. Read step times from majordomus history --json (task.started, task.refused, task.finished) and from the run clock where no ledger line is written. Commit the T1 trial record and regenerate the economics projections.

Why

This is the experiment T1 of the owner's report of 2026-10-19 asks for. It does not wait on I3127 (BLOCKED), because the ledger observes the task steps. A failed run is recorded and published, never retried silently.

Current state

lib/finish.sh:108 writes task.refused and :131 task.finished; lib/check.sh:51-58 writes no line for a refused check, so that refusal is timed by the run clock. No adoption record exists.

Desired state

At least one committed T1 record of an admitted repository; the T1 row reads a computed status.

Scope

• .ai/repo/benchmarks
• docs/generated/economics.json
• docs/generated/economics.md
• docs/generated/economics.yaml
• site/data/generated/economics.json

Out of scope

• Pushing to the adopted repository's remote
• Fixing what the run meets (I3365)
• Repository contents in the record

Dependencies

• I3362✕BLOCKED Candidate repositories are measured against the registered floors and admitted or refused before any of them is installed into

What waits on this

• I3364✕BLOCKED The adoption-overhead bench takes a target repository, and Majordomus's overhead and footprint are measured in the adopted foreign repository
• I3365✕BLOCKED Every intervention, undocumented command and refused step of a foreign adoption carries a friction id or a reason, and every friction id is cited by an issue or a cancellation

Acceptance criteria

• The record passes the loader and names its candidate
• Each timing names its source
• The agent and version and the count of manual interventions are recorded
• Each friction met has an id and a declared code
• If reached_accepted_finish is false, the record is committed anyway and the issue states what stopped it

Validation

• cargo test --manifest-path apps/majordomus-cli/Cargo.toml --test economics
• majordomus economics proof
• majordomus plan validate
• scripts/derive-check

Evidence required

• adoption_record_committed

Evidence

None recorded. Every token above needs a command or an artifact behind it before this issue can be completed; narrative is refused.

Timeline

started

—

verified

—

completed

—

Those three fields, the evidence above and the state of the dependencies are all the status is made of. There is no status field to disagree with them.

Canonical record: .ai/repo/project/issues/I3363.yaml. Read it back with majordomus plan show I3363.