I3359 — A workflow states which repository may be adopted as foreign, what each adoption records and publishes, and with whose consent
Write .ai/repo/workflows/foreign-repository-adoption.md: the selection measurements, each a command run at the adopted commit (tracked files, commits, primary language, existing test command, no .ai/ or .majordomus/ path or Majordomus region), with floors taken from an owner decision recorded before any candidate is measured; the publication basis (licence or the owner's dated written consent) and what a record may carry under each, including none; the steps as docs/ADOPTION.md states them, each naming where its time is observed (ledger event or run clock); the record fields; and what is never recorded (file contents, secrets, people's names). Link it from .ai/repo/workflows/README.md and docs/ADOPTION.md.
READY wave 0 · p0 · docs profile · parallel safe
Ready. Every dependency is done, so majordomus plan start I3359 will be accepted.
Objective
Write .ai/repo/workflows/foreign-repository-adoption.md: the selection measurements, each a command run at the adopted commit (tracked files, commits, primary language, existing test command, no .ai/ or .majordomus/ path or Majordomus region), with floors taken from an owner decision recorded before any candidate is measured; the publication basis (licence or the owner's dated written consent) and what a record may carry under each, including none; the steps as docs/ADOPTION.md states them, each naming where its time is observed (ledger event or run clock); the record fields; and what is never recorded (file contents, secrets, people's names). Link it from .ai/repo/workflows/README.md and docs/ADOPTION.md.
Why
T1 of the owner's report of 2026-10-19 requires a repository not created or structured around Majordomus. Without declared criteria any repository could be called foreign afterwards, and the critique noted that floors chosen by a worker who already knows the candidates are not pre-registered. The field names reached_accepted_finish and seconds_to_accepted_finish match I3129's, so the forms do not diverge.
Current state
git ls-files .ai/repo/workflows lists README.md, continuity.md, plan.md, task-lifecycle.md and use-cases.md. docs/ADOPTION.md:5-16 gives day-one commands and :165-169 removal, with no timing. I3129 (.ai/repo/project/issues/I3129.yaml) names reached_accepted_finish and seconds_to_accepted_finish.
Desired state
One linked workflow a worker can follow to admit a candidate and record one adoption without asking what counts.
Scope
- .ai/repo/workflows
- .ai/repo/workflows/README.md
- docs/ADOPTION.md
Out of scope
- The T1 protocol in the plan (I3360)
- Choosing a repository
- The outside-person form of I3129
Dependencies
None. This issue is a root of the graph.
What waits on this
Acceptance criteria
- Each selection measurement is a command with the place its floor comes from
- The publication basis distinguishes licence, owner consent and none, and lists what a record may carry under each
- The step list matches docs/ADOPTION.md and names each step's time source
- The workflow says nothing is pushed to the adopted repository's remote
- The workflows README lists it
Validation
- majordomus plan validate
- scripts/derive-check
- scripts/ci/english-only-check
Evidence required
- foreign_adoption_workflow
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/I3359.yaml. Read it back with majordomus plan show I3359.