Onboard crtahlin to the v2 ledger transport (and unblock repo access)

[plur9]

Your machine is not yet publishing to the v2 (DIP-0046) ledger transport, so work done locally has nowhere to land. Everything on the owner's side is already done — this issue is the part that runs on your machine, plus two access grants that are blocking you.

1. Get on the v2 transport

cd ~/Data && git pull                     # brings ledger_transport.py + the /wrap-up hook fixes

mkdir -p ~/.datacore
echo 'DATACORE_ACTOR=crt' >> ~/.datacore/identity

python3 .datacore/lib/actor_identity.py   # must print: crt (identity-file)
python3 .datacore/lib/ledger_transport.py sync

The identity file is not optional. Actor is never inferred from a hostname (DIP-0044 — one host is named bridge but writes as winston), so without it your events are refused or land under the wrong writer.

Done when .datacore/events/crt.jsonl appears in 1-datafund and 5-plur, and your commits start landing again.

2. If it still doesn't work, check these three

1. Does /wrap-up complete, or does it error on command_receipt.py / command_suggest.py? Those two hooks were missing/empty until 2026-09-09 (commands: make them findable, and make skipping one visible #175) — the git pull above is the fix.
2. Does python3 .datacore/lib/ledger_transport.py sync exist and run?
3. Had you pulled datacore at all since 2026-09-01?

Please report which of the three it was — it tells us whether anyone else onboarding will hit the same wall.

3. Repo access — blocked, needs the owner

You are a collaborator on datacore itself and on 8 private repos (datacore-crm, datacore-grants, datacore-mail, datacore-meetings, datacore-nightshift, datacore-space, datacore-telegram, datacore-trading), but you are not an org member, and two repos you need are not granted:

• datacore-chief-of-staff — required to install your own Winston
• datacore-app — required to run the desktop app

Also ungranted, in case they come up: datacore-appbuilder, datacore-dev, datacore-forge, datacore-fundraising, datacore-health, datacore-lens, datacore-testing, datacore-ventures, datacore-verity, module-metacognition.

Since 14 of 22 private repos are ungranted, an org membership or a team is probably cleaner than individual grants. That is an owner action — this issue is the record of what is blocked.

4. Not done, deliberately

• Credentials. An instance manifest scoping your host to 1-datafund and 5-plur is written but staged as .pending, with no ssh_alias, so nothing ships. Whether those spaces' credentials should sit on your machine is the owner's decision plus yours — not an automated one.
• Signing key. You have no verify_keys entry yet, so your events will be unsigned and v2_verify will say so. Generate one once you are publishing.

Full diagnosis and rationale: 2-datacore/1-tracks/ops/onboard-crt-to-v2.md.

[miles-on-nightshift]

Status check — 2026-09-14 (day 4, no follow-up)

Checked current state:

• datacore-chief-of-staff: crtahlin not a collaborator
• datacore-app: crtahlin not a collaborator
• Neither access grant has been issued yet

@crtahlin — have you completed step 1? Run these and report back:

cd ~/Data && git pull
mkdir -p ~/.datacore && echo 'DATACORE_ACTOR=crt' >> ~/.datacore/identity
python3 .datacore/lib/actor_identity.py   # should print: crt (identity-file)
python3 .datacore/lib/ledger_transport.py sync

Done when .datacore/events/crt.jsonl appears in one of the spaces. If /wrap-up errors on command_receipt.py, the git pull above is the fix.

@plur9 — repo access to unblock crtahlin (two commands):

gh api repos/datacore-one/datacore-chief-of-staff/collaborators/crtahlin -X PUT -F permission=write
gh api repos/datacore-one/datacore-app/collaborators/crtahlin -X PUT -F permission=write

This unblocks the Winston install and the desktop app — both required for D-011 (second operator). Once access is granted and crtahlin confirms the transport is syncing, this issue can close.