Public: anyone can read this; the crew can change it.
Forgify a business: origins mirror its repos in, extract pulls them apart, the crew writes the sync and pull adapters, and the result ships as its own forge #390
Nothing in the repository changed, so there is no commit and no push. This run was planning: I read docs/ORIGINS.md, docs/EXTRACT.md and docs/SPAWN.md, and opened three linked issues for #390. #383 is closed and the spawn design is docs/SPAWN.md. #420 (the spawn plan, which #439 waits on) is still open, and I didn't check it.
- #437, adapter app shape. An optional
adapterblock inforge.json(source host allowlist, schedule, typed config with secrets by reference). The adapter exposes an idempotentPOST /pullthat returns{pulled, skipped, cursor, errors}. The forge schedules the pull and records each one as a run, and outbound hosts are limited to the declared source. It also addsdocs/ADAPTERS.md, a template adapter, and the pull status on the app page. This one is ready to build. - #438, first two adapters. Real syncs built on the template, tested against recorded fixtures with no network in
bun test. It waits for #437. I can't tell which systems the owner means, so the issue asks @trevato to name the two systems and the data wanted. The crew shouldn't start it before they answer. - #439, prompt a business. Atlas turns a description into one validated plan of apps, adapters and the order between them. The plan is shown as a dry run first. Confirming opens the issues and dependencies through the existing planner path, with no duplicates, and the plan can feed the spawn plan. It waits for #437 and #420.
I did not write any adapter code, pick the two systems myself, or open pulls.
To follow the plan, see the map at /api/v1/repos/trevato/forge/map; #437 is the first one ready.
🤖 Generated with Claude Code
Parked by the crew: the run ended without a pull: no changes pushed: Nothing in the repository changed, so there is no commit and no push. This run was planning: I read docs/ORIGINS.md, docs/EXTRACT.md and docs/SPAWN.md, and opened three linked issues for #390. #
Parked by the crew: the check stayed red through 2 automatic tries (pull #467 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.
Parked twice; deferred behind the Later gate #595 (umbrella #594): forgify a business and adapters serve no pillar now. Nothing is dropped; the owner moves it out by unlinking it from the gate. Start it fresh from main when it comes back.
Released from Later to use the week's subscription: Behind pace: 75% of the week left with 17% of its time gone, reset 2026-11-15 02:00 UTC, burning 0% an hour against 0.5% allowed; speeding up to 5 of 5 slots and releasing the next issue.
Split into what is still left now that the forge calls /pull on a schedule (#10060). #10082: the forge's call is not signed, so the template refuses it. Fix that first. #10083: the Status section of ADAPTERS.md is out of date. #10084: a writer can run a pull now through the API and MCP. #10085 (the first two real adapters, which need you to name the systems) and #10086 (prompt a business) wait behind the Later gate.
The owner's work: bringing old systems into the forge means lots of custom sync/pull code against external systems plus the migrate feature; then handing the result out as a forge of its own; eventually 'prompt a business' — a description becomes a map of apps and integrations.
Planner: read docs/ORIGINS.md and docs/EXTRACT.md; open linked issues for (1) an 'adapter' app shape for syncing an external system (config, schedule, idempotent pulls, a contract the forge can audit), (2) the first two adapters as real work from the owner's businesses (ask him which), (3) 'prompt a business' → Atlas turns a description into apps + adapters as issues. Waits for the spawn design and #383.