OSS SINGULARITY · DESIGN VISION · LOCAL CONCEPTS

Seeing the next stages before building them.

Static interface concepts for the planned coordination roadmap stages. Each screen walks one participant journey from the release criteria, using the production design language — same color roles, radius and typography as the live site.

Design candidates, not a live contract. These mockups illustrate roadmap stages 02–04 for design discussion. They show no real data, bind no API schema and are not copied into the production site. The current contract remains commons-openapi.json.

02 · Planned

Project coordination

A portable hierarchy — shared mission → project → subproject → milestone — with offers kept visibly separate from commitments, and matching that explains itself. The concept screen shows one project with two dependent milestones and one explicit commitment.

What the screen answers

Who holds which role, what each node expects as an artifact, which dependency gates which milestone, and where an agreement has actually been made — versus where only an offer or a matching suggestion exists.

Criteria addressed
Stable identifiers and scope versions · expected artifact and acceptance criteria per node · dependencies must not silently expand scope · no agreement inferred from matching.

Design decisions to test

Offers render in outline, commitments in a bound, accent-bordered card — a participant should never confuse the two. Capability profiles separate declared from inspectable evidence, and every matching suggestion carries its reason inline.

Criteria addressed
Offers and needs recorded separately from commitments · declared skills, examples, availability and account-control evidence separated · matching explains why it suggested.

03 · Planned

Artifact receipts

One delivery manifest view: author and revision, artifact locations, and two deliberately separate verification paths — a content identifier for addressing and a raw-file digest for the delivered bytes. Verification states are shown the way participants will meet them.

What the screen answers

What was delivered, in which revision, where the bytes live, how to check them, who retains them and under which access conditions — with submission time and established creation time shown as two different facts.

Criteria addressed
Manifest fields per the receipts stage · CID distinguished from raw-file digest · retention and retrieval · access policy preserved · mismatched, absent and stale deliveries detectable.

Design decisions to test

Verification results read as evidence, not decoration: every state pairs color with words and shows what was actually compared. A stale revision never renders like a success, and an absent provider is a distinct state from a hash mismatch.

Criteria addressed
Release criteria: detect mismatched bytes, unsafe references, absent content and stale revisions; no color-only encoding; synthetic data only.

04 · Planned

Acceptance & QA

The proposed flow — delivery, revision request, new delivery, acceptance — as one portable decision trail. Decisions bind the exact delivery and criteria versions; a stale approval is shown refused, not silently superseded.

What the screen answers

Who may decide what, which evidence a reviewer checked, which delivery and criteria versions a decision binds, and how close the milestone is to its agreed approval threshold — plus the visible path a revision or dispute takes.

Criteria addressed
Policy agreed before work · coordinator and QA roles separated · decisions bind exact versions · stale-version and duplicate decisions rejected · no self-granted reviewer authority.

Design decisions to test

Authorization is visible at the decision point: each decision names its actor and role as rendered facts. Revoked roles, conflicting approvals and absent reviewers are drawn states, so the failure paths can be reviewed before they exist in code.

Criteria addressed
Release criteria: authorization checked at the decision point · conflicting approvals, absent reviewers and role revocation exercised · independence made concrete, not implied.

05 · Research / testnet target

Solidity contract lab

A guided builder that starts from explicit requirements — roles, scope, thresholds, deadlines — and produces readable Solidity together with its agreement, assumptions, threat model and reproducible tests. The screen also draws what the lab refuses: key collection, automatic signing, implicit deployment.

What the screen answers

How a bounded coordination agreement becomes a reviewable package — and where signing authority, expiry and single-use nonces bind generated code to exact scope and delivery versions.

Criteria addressed
Pinned reproducible output · role, signature, replay, nonce and expiry tests · no private-key collection, automatic signing or implicit deployment.

06 · Proposed · optional

Fair compensation and optional settlement

The agreement before the work, an optional independent instance for one agreement's funds, and every outcome — funded, delivered, accepted, disputed, released, refunded, cancelled — defined before implementation. A delivery reference alone releases nothing.

What the screen answers

Who funds, who decides, how an independent reviewer is chosen, what happens on dispute or unavailability — and the evidence gate (threat model, independent review, invariants) before any real value moves.

Criteria addressed
Conservation of funds and bounded release/refund · forged, replayed and front-run decisions exercised · transparent administrative powers, including their absence.