website/docs/project-brief.md

Website project brief

Brief revision 5, prepared 2026-10-18. This continues revision 4, retained in Git history. The Connect contributor entry is accepted source work through PR 29; its static publication was verified on 2026-10-18. The dated decision and continuation note records the later decision alongside the unchanged original handoff. The source pins identify inspected revisions, not a promise about moving branches.

Purpose and starting points

OSS Singularity is a shared home where people and agents can discover useful work, understand its sources and contribute deliberately. This website makes that purpose visible and connects it to practical collaboration in the Laboratorium. Preserve the purpose and the reasons for decisions when participants or implementations change.

This first path uses software we can inspect together. The broader home also serves research, art and collective projects; it is not limited to a coding workflow.

• Shared mission and its public room.
• Website repository and contribution guidance.
• Connect project path: discover → understand → draft → return.
• Contributor guide: one useful contribution with an agent, without needing programming skills.
• Continuation composer: carry purpose, results, decisions, sources and one next action into a portable brief.

Where to continue

Fact	Current record
Concrete result reached	The first Website project path, contributor Guide, offline continuation Composer and Connect contributor entry are accepted source work. A fresh AI reader checked the original Connect contribution using public sources. The Composer's earlier static publication and the new Connect entry's publication are verified.
Canonical Laboratorium evidence	Maintainer ClaudiuSchuster merged the Guide and brief revision 3 in PR 25 at 3fec7e031761fcacbccb15af508cd064120c8143, and the Composer in PR 27 at ecb120bc11b8bfedd20a24b94e03943fc2e039d6. The Connect contributor entry was later accepted in PR 29. The pinned publication records below establish the corresponding static results. These decisions and AI reader exercises do not establish human usability.
One next action and permission	Draft one small real non-software project brief with a purpose, an evidenced starting state and exactly one bounded contribution for a new human participant, optionally with an agent. Permission is draft only using public or explicitly supplied sources. Outreach, signup, account actions, submission and deployment are outside this permission. Do not invent a completed project or participant, or describe the draft as a human study.

Public source baseline and observations

Source	Revision and use
Revision-2 brief contribution	PR 23 merged as Website commit 4f6abcb8cdcb511f5d6d57651c883e6d8b3d8d1d, which carries revision 2 of this brief and the fresh-reader observation. The maintainer decision on that contribution is a matter of public record in the PR.
Accepted Guide and revision-3 brief	PR 25 was merged on 2026-10-16 as 3fec7e031761fcacbccb15af508cd064120c8143. The Guide and its agent continuation record are pinned there. Their pre-merge descriptions of pending acceptance remain historical; the PR records the later maintainer decision.
Accepted offline continuation Composer	PR 27 was merged on 2026-10-16 as ecb120bc11b8bfedd20a24b94e03943fc2e039d6. Its contract describes local Markdown/JSON composition and the limits of reported acceptance. The tool does not verify its author's claims or submit work.
Published project path and revision 1	PR 22 merged as Website commit 5fbf219c82ca2d346a3ed1e2b434f0348a7137f9, tree 2bf3e57f04605717584ae3f1efd6697c4a6bfcb1. The live Connect path exposes discover → understand → draft → return.
Earlier project-path publication	At ledger commit 38b48a51533a99080d208aa8817c5547e947a32a, the intent binds Website 5fbf219… to run 260930000000011, attempt 1; the outcome records production-static, verified, success. These records establish the reported publication outcome, not contributor acceptance.
Composer static publication	At ledger commit d36b178eaa71521cef4ade87b3219338466ac597, the intent binds Website ecb120bc11b8bfedd20a24b94e03943fc2e039d6 to run 260930000000012, attempt 1; the outcome records production-static, verified, success. Read on 2026-10-17. This is a publication record, not evidence that a newcomer completed a contribution.
Accepted Connect contributor entry	PR 29 records the maintainer's merge on 2026-10-17 as 6e70166, following review of the final source. The dated decision note records its fresh-reader check and continuation. The publication intent binds that source to run 260930000000014, attempt 1; its outcome records production-static, verified, success. Verified on 2026-10-18.
This contribution's starting revision	Accepted Website main at 014dcb8d4f7d6ce0632d8a6d9e5cfb9462a26b91, following documentation PR 28. This includes the Guide and Composer sources above. It is newer than the published static revision and does not itself imply a new static publication.
Mission-room handoff	Controller at the revision-1 baseline. Produces the public mission brief, not a record of agent execution.
Project coordination	Project controller at the revision-1 baseline and published API contract. Projects, milestones and public exports already exist.
Laboratorium public reader	Revision-1 implementation pin: commit ad99aae2b48bfa9d68af2294eb00a9dbec824407, tree cec0eab20c3e88c8f408674d001c4c3e47e5cfab. Anonymous endpoint: https://oss-oo.io/mcp/public. An anonymous POST tools/list on 2026-10-15 returned the four reader tools listed below. This checks discovery only; the source pin does not attest the current deployment or a complete file read.

Read the latest brief and current public mission before acting. For each source used in a contribution, retain its URL, exact revision where available, relevant path and the observation it supports. A source date or successful download is not a quality or completion verdict.

An agent with an already configured public reader can use public_search_repositories, public_repo_info, public_list_tree and public_get_file. Tree/file continuations must retain the returned immutable reference and repeat the same owner/repository; read every page/chunk before claiming completeness. Ordinary public source links work without that integration. This brief does not install a plugin or grant access to a tool.

Decisions and reasons

Decision	Reason
Start with the real Website repository and a proposed contribution.	A reader can inspect its purpose and source without inventing an open job or a successful demonstration.
Use public reading first; carry a checked draft into the existing repository review flow.	Understanding, permission to change source, submission, acceptance and publication are different decisions.
Keep this brief in Git alongside the project.	Sources, rationale and next steps should survive a new chat, tool or contributor without a separate memory service.
Link the accepted contributor Guide directly from Connect.	A person without programming experience needs a visible explanation of choosing, checking and handing off one small contribution before navigating source files. The existing Guide supplies that path.
Keep a compact continuation checkpoint and use the existing Composer.	A fresh participant needs the concrete result, its actual decision record and one permission-bound next action. More storage or a new project selector does not supply that evidence.
Reuse mission/project exports and link actual delivery decisions.	Existing coordination records retain their meaning; a parallel project database would duplicate them. A published field note is not automatically an accepted result.
Keep the Mission Lab simulation labelled as illustrative.	A planned observe/plan/build/review/handoff sequence does not prove that any of those actions happened.
Keep account recovery in Connect and retain current identity boundaries.	Anonymous source reading needs no account. Commons account-control proof does not establish Laboratorium access or permission to post.
Add a practical guide for contributing with an agent without programming skills.	The shared home serves more than coding; the public entry points, non-coding paths and review boundaries needed to describe one honest loop already exist.

Accepted contribution: a visible Guide entry and continuation checkpoint

PR 29 accepted a direct entry from Connect to the contributor Guide. The entry names wording, research and a reader observation as useful non-coding contributions. The Guide's introduction now links its actual PR-25 decision and keeps human usability testing open. The brief records the accepted Guide and published Composer, and the ideas register separates the current Laboratorium domain from the still-planned Commons API alias.

The author used the existing Composer to prepare a source-bound continuation in Markdown and JSON. These unchanged browser exports pin the originally proposed source at 297e240895027a52c96a9a640fd6851cfb7af165, the accepted earlier milestones and the inspection action authorized at that time. Their proposed status remains a truthful historical snapshot. The 2026-10-18 decision note adds the fresh-reader result, later maintainer decision, verified publication and current next action without rewriting either export.

Scope: the static Connect entry and the directly relevant project documentation. This contribution uses existing links, styles and review paths. It does not add a store, selector, backend or automatic submission. The original contribution was AI-authored. Its source review, fresh AI reader check, maintainer decision and verified static publication are now recorded. No human usability test is claimed.

Acceptance criteria:

1. Factual claims link to public sources and immutable revisions where available; partial reads and uncertainty are explicit.
2. Accepted source work, published static content and proposed next work remain distinguishable. Missing or unsuccessful checks cannot become success claims.
3. A fresh person or agent can follow Connect to the Guide and brief, then explain the purpose, accepted milestones, open work and one next action from the brief and its linked public sources. The changed entry must remain usable by keyboard, on narrow screens and in both themes.
4. A continuation composed from the actual sources and decisions preserves those distinctions in Markdown and JSON. An independent participant checks it; the author's own export or checks are not independent acceptance. Any later maintainer decision must link to the exact reviewed artifact revision.
5. No credentials, private conversations, personal project data or operational access details enter the brief or the guide.

Evidence and open work

Item	What is established	What remains open
Existing mission/project exports	Their implementations and limits are inspectable at the revision-1 source pins above. Mission handoff contract and coordination roadmap describe them.	Exports and the Mission Lab illustration do not establish that a contribution was performed or accepted.
First project path and revision 1	PR 22 records the merge; the pinned intent/outcome above record successful verified static publication. The live Connect source contains the path.	Publication does not establish a newcomer's understanding or a complete contribution journey.
Fresh-reader exercise	One fresh agent read the first revision-2 draft and five linked source files completely through the installed MCP reader. A separate coordinating reviewer checked byte/blob identity and accepted the limited observation.	One agent and single-chunk reads do not establish human usability, multi-chunk continuation, installation, live-site behavior or a complete contribution journey.
Guide and revision-3 contribution outcome	PR 25 records the maintainer's merge at 3fec7e031761fcacbccb15af508cd064120c8143. The continuation record describes the earlier fresh agent pass.	The pass exercised the Guide text only. Its later source acceptance is not a human usability test or a complete contribution journey.
Offline continuation Composer	PR 27 records source acceptance at ecb120bc11b8bfedd20a24b94e03943fc2e039d6; the pinned run-12 records above report successful verified static publication.	A generated brief records its author's claims. It does not establish their truth, confer permission or prove another participant can continue correctly.
Connect contributor entry	PR 29 accepted the reviewed source. A fresh AI reader check completed the original public-inspection action against the earlier candidate.	The earlier reader did not inspect the later final source or deployment. A separate live desktop keyboard check followed Connect → Guide → brief after publication; live mobile behavior and human usability were not tested in that check.

One fresh reader could identify a useful next step on revision 2, and a fresh agent continued the Guide text on 2026-10-16. The Connect contribution now adds a real source change, a public-source check by another AI participant and actual maintainer acceptance. Its publication is verified through the run-14 records above. This later documentation checkpoint records that result; it does not announce another static release. The next draft explores one non-software project as a bounded step toward the broader shared home; it does not complete that product goal. Agent exercises stay labelled as agent exercises. Capability matching, independent QA/disputes, authenticated agent contributions and settlement are separate roadmap work; none is required for this public reading-and-draft path.

Review and integration authority belong to the project's maintainers under CONTRIBUTING.md. The single next action is the draft in Where to continue. Any later source contribution, submission, acceptance or publication follows its own authorization and the normal project review flow.

A later brief revision should retain the purpose, link the revision it replaces, record actual reader findings and decisions with reasons, and bind any acceptance to its exact public artifact. Keep unsuccessful attempts and evidence gaps visible, then end with one next action and its required permission. Reflect a result on Singularity as accepted work only after real acceptance.