One project, two dependent milestones, one explicit commitment. Offers stay
outline; commitments are bound. Every node names its scope version, expected artifact and
acceptance criteria; every suggestion explains itself.
Design candidate. Illustrates the planned coordination stage's
release criteria with synthetic content. Not a live API, schema or product page — see the
vision index for scope.
Journey view · portable hierarchy
Project tree
Shared mission → project → subproject → milestone. Dependencies render as an
explicit gate on the dependent node; a scope change request renders as a badge, never as an
automatic expansion.
Purpose: make artifact verification usable for independent reviewers.
Roles: coordinator @aria · reviewer slot open · contributors by commitment.
Milestone: Digest verifierscope v1committed
Expected artifact: delivery manifest with raw-file digest instructions.
Acceptance: two independent verifications of the same synthetic bytes.
Milestone: CID explainerscope v1blocked by · Digest verifier
Dependency: cannot start before the verifier exists. A dependency
gate is a visible condition, not a silent scope expansion.
Criteria addressed
Stable identifier, scope version, purpose, parent, dependencies, expected artifact, acceptance
criteria and agreed roles per node · dependencies must not silently expand a participant's scope.
Journey view · offers versus commitments
Offer and commitment are different states
An offer is one participant's input. A commitment binds two or more participants to
a scope version, review responsibility and change/exit terms. The visual difference is deliberate:
outline card for the offer, accent border and bound badges for the commitment.
Offerno agreement yet
"I can build the digest verifier in the first half of October."
Posted by @kofi toward Verification toolkit · scope v2. Nothing is agreed; posting an
offer assigns no task and grants no role.
Criteria addressed
Offers and needs recorded separately from actual commitments · publishing a card does not
assign a task.
Commitmentbound · scope v1
Participants
@kofi (contributor) · @aria (coordinator, review)
Scope version
Milestone: Digest verifier · scope v1
Contribution
Verifier script + delivery manifest for synthetic bytes
Review responsibility
@aria checks scope; QA role checks evidence
Terms
Voluntary · change or end by request from either side
Criteria addressed
A commitment names participants, agreed scope version, contribution, review responsibility,
budget or voluntary terms, and how either side can request a change or end the arrangement.
Journey view · capability and matching
Profiles separate claims from evidence — and matching explains itself
Declared skills, inspectable examples, availability and account-control evidence
are different columns, never mixed. A matching suggestion renders with its reason; it never
claims a skill was verified.
One linked synthetic verification run with its own manifest
Availability
Weeks 41–44, ~6 h/week
Account control
GitHub identity @kofi-syn — proves control of that account, nothing else
Criteria addressed
Capability profiles separate declared skills, inspectable examples, availability and external
account-control evidence · participant type supplies no privilege, verification level or ranking.
Matching suggestionwhy this was suggested
Suggested for Milestone: Digest verifier because its declared skill
matches the expected artifact and an inspectable example exists. Not verified: skill
quality and review outcome remain open until acceptance decisions exist.
Criteria addressed
Matching must explain why an opportunity was suggested; it must not claim a skill was verified
when only an account or self-description was checked · no agreement inferred from a suggestion.