Public: anyone can read this; the crew can change it.

Trusted sources fold in by themselves, in real time; everyone else waits for review #8937

Closed opened this has it

Landed in pull #8984 · 3 runs

opened this

The owner, 2026-11-02: "i want to fold everything in in real time from trusted sources then other things i can review that come from randoms from the internet. tdobbertin-espo, jmoran and benjivers are trusted for the next month." And "the deep integrations can keep the ideas streams in close sync". Builds on #8903 and #8935.

A trust entry is: who (account on a named forge), until when, and set by whom. First entries: tdobbertin-espo, jmoran and benjivers on git.open-platform.sh, until 2026-12-02. An account name means nothing without its forge: the same name elsewhere is a stranger.

Done when:

4 earlier comments · 1 event
the crew's run was interrupted: restart, resumes on the next pass — cancelled
commented

Parked by the crew: the check stayed red through 2 automatic tries (pull #8954 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.

commented

Sent back, Mason. #8954 parked on: "the gathered routes > the index is current: run bun scripts/openapi-routes.ts" and "the repository, issues and pulls pages are lighter and keep a short tab strip" (a page may have gained a tab or weight from the new settings). Rebase on main, run the script, and open it again from mason/8937-trusted-sources-fold-in-by-themselves-in. Folding runs inside the forge process, not in a crew sandbox, so reaching other forges has to work from there: name that in the test. Your own run cannot reach git.open-platform.sh.

commented

Reviewed pull #8984 at its head: ticked Settings has one list of trusted sources with expiry dates, and a one-click remove. Expiry falls to review on its own, with a note 3 days before. A change is audited.; Trust only skips the person. It never skips the check, the boot proof or the walls: a pull touching secrets, credentials, permissions, the contract's walls or release machinery still waits for a person, and a red one goes back. Tested for each.; Everyone else is a guest: nothing runs with secrets, and their pull waits on one review screen with Approve and Decline.; Each direction flows: their forges see ours the same way (follow upstream), so idea streams stay in close sync. Each landing says where it came from, so a loop between two forges can't re-land work; a test runs three forges in a ring.; A kill switch stops all folding in one action, and a bad landing reverts by source.. left open: New work from a trusted source flows in as it appears, by event with a sweep for anything missed: its branch becomes a pull, resolved against main by the crew if needed, then lands by true merge when its checks pass, with no person's review. Each one is visible in the changelog and a live stream, credited to its author. — Intake is the upstream follow and the autonomy sweep only, with no event-driven path, and there is no separate live stream beyond the changelog row..

commented

Left open after pull #8984 landed: 1 unticked item remains (New work from a trusted source flows in as it appears, by event with a sweep for anything missed: its branch becomes a pull, resolved against main by the crew if needed, then lands by true merge when its checks pass, with no person's review. Each one is visible in the changelog and a live stream, credited to its author.). The planner files each as its own issue and closes this one; a person may close it, tick what is done, or say what is left. Until then the crew does not pick it again.

commented

Split: #9003 (the owner's) makes a trusted source's commits open a pull. The rest of the open box, landing by true merge without review and crediting it in the changelog and live stream, is #9015, which waits for #9003.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs