Repository navigation
docs(plans): the SourceOrigin platform plan is kept in the repository - #527
Draft
PiquelChips wants to merge 6 commits into
Draft
PiquelChips wants to merge 6 commits into
PiquelChips wants to merge 6 commits into
Conversation
The planning discussion for the platform that hosts Origin repositories only existed in a chat thread. docs/plans/platform records every decision, proposal and open question from it: the roadmap, what the platform needs from Origin, the platform itself, the frontend, and the repository, CI and deployment. Plans stay out of the book, so nothing is published.
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: true
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. |
This was referenced Nov 13, 2026
Closed
…pen stack already has Reading Origin's open stack showed that nothing in it has to change for hosting: principals need no format change, sign-in has its seam, and the storage boundary can wait. The plan now records that, Origin's four milestones with their epics and issue numbers, the repository registry, how colocated mode works, and that the plan is kept current as decisions are made.
This was referenced Nov 13, 2026
…ding Three reviewers found that milestone 1 could not be reached as written and that several format and security decisions were missing. The plan now records each finding and its outcome: ignore files and times on records in Origin's v0.1, one issuer per repository, a repository identity in genesis, redaction, a wider sign-in seam, no automatic CI at first, private repositories by default, reviewed marks in PostgreSQL, folders as the only hidden paths, and the mirror continuing git's history. Issues are written with their repository.
This was referenced Nov 13, 2026
…ackups are decided Repositories are never created implicitly: the platform calls an explicit create on a private listener of the node. Changes can be made private by choice, in place of hiding them automatically. Backups stop the node, and a restored node takes back what it signed. Sign-in stays in Origin Auth while its settings, developer console and admin dashboard move to the product's frontend.
…ions The account settings get a hostname of their own, and the name lookup returns handles from the start.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The plan for the SourceOrigin platform, the service that will host Origin repositories, only existed in a planning thread. A context compaction or a dead disk would have lost it.
This saves it in the repository, under
docs/plans/platform/, with every decision, proposal and open question from the discussion:README.md: the goal, the decisions at a glance and the open questions.roadmap.md: the milestones, and where Origin, SourceOrigin and piqueld stood.origin.md: what the platform needs from Origin.platform.md: what SourceOrigin stores, its services, hosting, integrations and product ideas.frontend.md: why Topcoat goes, and the experiment that picks between React and SvelteKit.repository.md: the layout, the databases, the piqueld applications, CI by area and the tests to add.notes.md: the original notes, unchanged.Plans are not listed in
docs/SUMMARY.md, so the book publishes none of this. The documentation guide andAGENTS.mdnow say where plans live.This is a draft: it is here to keep the documents safe, and the plan will change as the discussion goes into practical depth.
Council review
Rounds: 1
A review of the design itself, not of code. The findings are being discussed before the plan changes.
Note
Written by Claude Fable 5.2 in Claude Code, and reviewed by GPT 6.1 Sol, Claude Opus 5.5 and Claude Fable 5.2 (via T3 Code)