01 / Show the vision
$EYE / MY3YE
Define the opening, explain the funding and establish accountable custody.
The work ahead
A whole system.
A place for your part.
Build a capability. Teach a skill. Review the work. Help a community acquire what it needs. Every contribution should leave a useful record and have clear terms.
Separate openings. Connected work.
Start with the chapter you care about.
02 / Build the story
PiPi & the Pen
Shape the lore, keep contribution records and build PiPi’s first sourced answers.
03 / Make the music
Otto Music
Prepare a shared album, preserve credits and improve the platform together.
These are starting points for the proposed launches, not complete release checklists. Shared dependencies, funding and final scope still need review. Launch dates are to be announced.
First proposed coordination mission
The Pen builds PiPi.
Write a scene. Draw a character. Find a contradiction. Test an answer. Help shape PiPi’s lore and the approved knowledge behind KOINK FUN’s future AI guide. This small mission lets us learn how people create, review and keep credit together.
Introductions are open. Try the Pen simulation now. The shared submission service, permissions and review process are launch goals. Paid work needs an agreed budget before it begins; participation does not automatically grant tokens or governance weight.
01 / Define the need
Manifest connects the outcome to work, resources, dependencies and an accountable owner.
02 / Agree and deliver
SideGigs is intended to coordinate funded work with acceptance evidence and independent review.
03 / Carry it forward
Bloom records learning and attribution. Umahn will carry scoped reputation, with review and appeal. Financial rewards and decision-making authority follow separate rules.
Find your contribution
37 of 37 work packages
L01 / KOINKDefine the issuer, offering route and round rightsQualified counsel · Founder / issuer representativeProposed · Unfunded · View requirements
What acceptance requires
- No categorical meme-token exemption claim
- Actual route approved before accepting affected funds
Evidence to deliver
- Entity and participant geography
- Written offering assessment
- Published round rights and restrictions
Resources needed
Depends on
No preceding work package listed. Funding, assignment and review terms still need agreement.
Independent review. No self-approval.
Cash: budget to be agreed and reserved. Tokens: no approved allocation. Reputation: evidence and a scoped review. Governance: separate impact assessment under an agreed policy.
Your introduction will include reference L01. It does not assign the task or create a paid agreement.
L02 / ManifestImplement versioned project, need, milestone and receipt recordsProtocol designer · Full-stack engineerProposed · Unfunded · View requirements
What acceptance requires
- One stable ID per economic origin
- Private payload pointers excluded from public commitments
- Dependencies and amendments are explicit
Evidence to deliver
- Versioned schemas and migrations
- Signed receipt fixtures
- Replay and unauthorized-mutation tests
Resources needed
Depends on
No preceding work package listed. Funding, assignment and review terms still need agreement.
Independent review. No self-approval.
Cash: budget to be agreed and reserved. Tokens: no approved allocation. Reputation: evidence and a scoped review. Governance: separate impact assessment under an agreed policy.
Your introduction will include reference L02. It does not assign the task or create a paid agreement.
L03 / SideGigsSnapshot funded escrow terms and all settlement recipientsSolidity engineer · Independent contract reviewerProposed · Unfunded · View requirements
What acceptance requires
- Changing defaults cannot alter previously funded payouts
- Arbitrator authority and replacement terms fixed in the funded agreement
Evidence to deliver
- Per-gig immutable term records
- Admin-change regression tests
- Settlement and refund reconciliation
Resources needed
Depends on
No preceding work package listed. Funding, assignment and review terms still need agreement.
Independent review. No self-approval.
Cash: budget to be agreed and reserved. Tokens: no approved allocation. Reputation: evidence and a scoped review. Governance: separate impact assessment under an agreed policy.
Your introduction will include reference L03. It does not assign the task or create a paid agreement.
L04 / SideGigsMake disputes and missing-review outcomes live and defensibleMechanism designer · Solidity engineer · Dispute specialistProposed · Unfunded · View requirements
What acceptance requires
- Earliest reveal alone cannot establish accepted quality
- No indefinite lock from an unavailable arbitrator
- Release requires declared acceptance policy
Evidence to deliver
- No-ranking and absent-arbitrator policy
- Deadline and appeal tests
- Unusable-deliverable challenge exercise
Depends on
Independent review. No self-approval.
Cash: budget to be agreed and reserved. Tokens: no approved allocation. Reputation: evidence and a scoped review. Governance: separate impact assessment under an agreed policy.
Your introduction will include reference L04. It does not assign the task or create a paid agreement.
L05 / KOINKImplement real rounds, deposit receipts and tranche accountingSolidity engineer · Payments engineerProposed · Unfunded · View requirements
What acceptance requires
- Receipts only after actual escrow settlement
- Round terms bound to funded positions
- Exact fee path modeled
- No use of localStorage as money ledger
Evidence to deliver
- Pinned funding-core decision
- Verified testnet contracts
- Successful funding, payout and refund flows
Resources needed
Depends on
Independent review. No self-approval.
Cash: budget to be agreed and reserved. Tokens: no approved allocation. Reputation: evidence and a scoped review. Governance: separate impact assessment under an agreed policy.
Your introduction will include reference L05. It does not assign the task or create a paid agreement.
L06 / KOINKAdd multi-asset funding routes and failure recoveryCross-chain integration engineer · QA engineerProposed · Unfunded · View requirements
What acceptance requires
- BTC, SOL, ETH, stablecoins and PIPI enabled individually only when supported
- No duplicate receipt on retry or reorganization
- Conversion risk disclosed
Evidence to deliver
- Executable route quotes
- Asset/network allowlist
- Finality, expiration, underpayment and refund tests
Resources needed
Depends on
Independent review. No self-approval.
Cash: budget to be agreed and reserved. Tokens: no approved allocation. Reputation: evidence and a scoped review. Governance: separate impact assessment under an agreed policy.
Your introduction will include reference L06. It does not assign the task or create a paid agreement.
L07 / SOSEstablish treasury custody, limited authority and incident operationsTreasury operator · Security engineer · Independent signersProposed · Unfunded · View requirements
What acceptance requires
- Multiple keys not misrepresented as independent people
- Agent spending is scoped and capped
- Monitoring reconciles liabilities and balances
Evidence to deliver
- Signer-control disclosures
- Verified treasury configuration
- Recovery and incident exercises
Resources needed
Depends on
Independent review. No self-approval.
Cash: budget to be agreed and reserved. Tokens: no approved allocation. Reputation: evidence and a scoped review. Governance: separate impact assessment under an agreed policy.
Your introduction will include reference L07. It does not assign the task or create a paid agreement.
L08 / UmahnImplement vouched personhood, recovery and scoped proofsIdentity engineer · Privacy specialist · Community admission reviewersProposed · Unfunded · View requirements
What acceptance requires
- Wallet rotation does not duplicate a person
- Admission assurance honestly stated
- Cross-provider identities not blindly summed
- No rights exclusion for absent proof
Evidence to deliver
- Admission rubric
- Nullifier and revocation tests
- Recovery and false-rejection appeal exercise
Resources needed
Depends on
Independent review. No self-approval.
Cash: budget to be agreed and reserved. Tokens: no approved allocation. Reputation: evidence and a scoped review. Governance: separate impact assessment under an agreed policy.
Your introduction will include reference L08. It does not assign the task or create a paid agreement.
L09 / UmahnImplement portable scoped reputation and appealsCredential engineer · Reputation researcher · Accessibility reviewerProposed · Unfunded · View requirements
What acceptance requires
- No global social score
- Ratings cannot directly mint governance
- Sample size and evidence visible
- Private disputes not broadcast
Evidence to deliver
- Signed reputation schema
- Interaction-backed ratings
- Conflict, revocation and appeal tests
Resources needed
Depends on
Independent review. No self-approval.
Cash: budget to be agreed and reserved. Tokens: no approved allocation. Reputation: evidence and a scoped review. Governance: separate impact assessment under an agreed policy.
Your introduction will include reference L09. It does not assign the task or create a paid agreement.
L10 / SideGigsVerify participant eligibility and deliverable usabilityIdentity integration engineer · Work-market designerProposed · Unfunded · View requirements
What acceptance requires
- Self-declared provenance cannot pass human-only eligibility
- Hash presence alone cannot pass deliverable acceptance
Evidence to deliver
- Proof-bound human policy
- Decryption/access and acceptance tests
Resources needed
Depends on
Independent review. No self-approval.
Cash: budget to be agreed and reserved. Tokens: no approved allocation. Reputation: evidence and a scoped review. Governance: separate impact assessment under an agreed policy.
Your introduction will include reference L10. It does not assign the task or create a paid agreement.
L11 / BloomIssue portable credentials and licensed attribution receiptsCredential engineer · Learning designerProposed · Unfunded · View requirements
What acceptance requires
- Credentials distinguish skill, issuer judgment and causal impact
- Duplicate origin cannot multiply rewards
- Royalties require explicit agreement
Evidence to deliver
- Issue, verify, revoke and export lifecycle
- License-aware lineage examples
Resources needed
Depends on
Independent review. No self-approval.
Cash: budget to be agreed and reserved. Tokens: no approved allocation. Reputation: evidence and a scoped review. Governance: separate impact assessment under an agreed policy.
Your introduction will include reference L11. It does not assign the task or create a paid agreement.
L12 / BloomReplace unchallengeable reward roots with accountable allocationProtocol engineer · Independent allocation reviewerProposed · Unfunded · View requirements
What acceptance requires
- Reporter signature alone does not settle disputed attribution
- Root sum cannot exceed reserved funding
- Private evidence remains selectively reviewable
Evidence to deliver
- Reproducible allocation inputs
- Challenge process
- Budget-conservation and double-claim tests
Depends on
Independent review. No self-approval.
Cash: budget to be agreed and reserved. Tokens: no approved allocation. Reputation: evidence and a scoped review. Governance: separate impact assessment under an agreed policy.
Your introduction will include reference L12. It does not assign the task or create a paid agreement.
L13 / ManifestImplement resource acquisition, ownership and lifecycle governanceProcurement designer · Full-stack engineer · Asset stewardProposed · Unfunded · View requirements
What acceptance requires
- Title and access distinct from token record
- Lifetime costs and replacement reserves included
- Accepted purchase creates linked installation and maintenance work
Evidence to deliver
- Request-to-acquisition workflow
- Offer evaluation and conflict records
- Custody, maintenance and retirement demo
Resources needed
Depends on
Independent review. No self-approval.
Cash: budget to be agreed and reserved. Tokens: no approved allocation. Reputation: evidence and a scoped review. Governance: separate impact assessment under an agreed policy.
Your introduction will include reference L13. It does not assign the task or create a paid agreement.
L14 / OttoImplement private capsules and user-controlled accessPrivacy engineer · Agent engineerProposed · Unfunded · View requirements
What acceptance requires
- Shared governance cannot decrypt personal memories by default
- Plaintext gateways and logs assessed
- Deletion limits honestly stated
Evidence to deliver
- Threat model
- Cross-user isolation tests
- Access revocation, retention and export exercises
Resources needed
Depends on
Independent review. No self-approval.
Cash: budget to be agreed and reserved. Tokens: no approved allocation. Reputation: evidence and a scoped review. Governance: separate impact assessment under an agreed policy.
Your introduction will include reference L14. It does not assign the task or create a paid agreement.
L15 / OttoBenchmark and implement governed self-improvementAI researcher · Evaluation curator · Independent red-team reviewerProposed · Unfunded · View requirements
What acceptance requires
- Agent cannot ratify own change or change constraints
- Quality, privacy, cost and latency measured
- Failed attempts recorded
- Execution claims match measured mode
Evidence to deliver
- Local, attested and on-chain comparison
- Held-out evaluation
- One improvement proposal, canary and rollback
Resources needed
Depends on
Independent review. No self-approval.
Cash: budget to be agreed and reserved. Tokens: no approved allocation. Reputation: evidence and a scoped review. Governance: separate impact assessment under an agreed policy.
Your introduction will include reference L15. It does not assign the task or create a paid agreement.
L16 / SOSDesign impact settlement, power limits and representationMechanism researcher · Community facilitators · Independent adversarial reviewersProposed · Unfunded · View requirements
What acceptance requires
- Capital and work distinct
- Per-person limits aggregate proxies
- No cap renormalization loophole
- Affected people retain a voice
- Simulation never awards actual standing
Evidence to deliver
- Software and care/resource-specific rubrics
- Capture and paralysis scenarios
- Ratified identity, delegation and quorum policy
Resources needed
Depends on
Independent review. No self-approval.
Cash: budget to be agreed and reserved. Tokens: no approved allocation. Reputation: evidence and a scoped review. Governance: separate impact assessment under an agreed policy.
Your introduction will include reference L16. It does not assign the task or create a paid agreement.
L17 / SOSInventory and independently value three years of founding contributionsFounder evidence compiler · Independent valuation reviewersProposed · Unfunded · View requirements
What acceptance requires
- Founder does not approve own claim
- Prior contributions require evidence and independent valuation
- IP rights and overlapping claims resolved
- Compensation does not confer permanent control
Evidence to deliver
- Dated artifact and expense dossier
- Prior compensation and collaborator ledger
- Reviewed bounded compensation proposal
Resources needed
Depends on
Independent review. No self-approval.
Cash: budget to be agreed and reserved. Tokens: no approved allocation. Reputation: evidence and a scoped review. Governance: separate impact assessment under an agreed policy.
Your introduction will include reference L17. It does not assign the task or create a paid agreement.
L18 / KOINKSpecify token issuance, cash rewards and rebalancingMechanism designer · Treasury analyst · Smart-contract engineerProposed · Unfunded · View requirements
What acceptance requires
- No cash promises backed only by FDV
- No automatic mint from activity counts
- Unreleased escrow cannot pay unrelated awards
- Existing rights not silently rewritten
Evidence to deliver
- Token-rights and dilution scenarios
- Cash-liability model
- Versioned mint limits and vesting
Resources needed
Depends on
Independent review. No self-approval.
Cash: budget to be agreed and reserved. Tokens: no approved allocation. Reputation: evidence and a scoped review. Governance: separate impact assessment under an agreed policy.
Your introduction will include reference L18. It does not assign the task or create a paid agreement.
L19 / TusitaAcquire feasibility resources and define the physical pilotLocal project coordinator · Qualified physical-domain professionals · Procurement leadProposed · Unfunded · View requirements
What acceptance requires
- 10k package is feasibility not a resort build
- Title/lease and professional approvals evidenced
- No purchased people or governance over personal autonomy
Evidence to deliver
- Site-access alternatives
- Costed feasibility and dependencies
- Community asset governance agreement
Resources needed
Depends on
Independent review. No self-approval.
Cash: budget to be agreed and reserved. Tokens: no approved allocation. Reputation: evidence and a scoped review. Governance: separate impact assessment under an agreed policy.
Your introduction will include reference L19. It does not assign the task or create a paid agreement.
L20 / SOSProve the complete funding-to-capability lifecycleIntegration engineer · Independent QA participantsProposed · Unfunded · View requirements
What acceptance requires
- One origin and balanced ledger across all applications
- Public claims match real statuses
- Unfunded tasks visibly distinguishable from paid agreements
Evidence to deliver
- Funding-to-Manifest-to-SideGigs-to-Bloom trace
- Resource procurement trace
- Failure and appeal exercise
Resources needed
Depends on
Independent review. No self-approval.
Cash: budget to be agreed and reserved. Tokens: no approved allocation. Reputation: evidence and a scoped review. Governance: separate impact assessment under an agreed policy.
Your introduction will include reference L20. It does not assign the task or create a paid agreement.
L21 / PiPiPrepare cultural participation and early-backer recordsArtist · Writer · Community organizerProposed · Unfunded · View requirements
What acceptance requires
- PIPI optional funding asset
- No guaranteed future airdrop claim
- Cultural contributions have documented authorship and compensation
Evidence to deliver
- Licensed cultural artifacts
- Eligibility and budget policy
- Receipt and claim appeal demo
Resources needed
Depends on
Independent review. No self-approval.
Cash: budget to be agreed and reserved. Tokens: no approved allocation. Reputation: evidence and a scoped review. Governance: separate impact assessment under an agreed policy.
Your introduction will include reference L21. It does not assign the task or create a paid agreement.
L22 / SOSIndependently review and rehearse production financial releaseIndependent security reviewer · Release engineer · Treasury operatorProposed · Unfunded · View requirements
What acceptance requires
- No unresolved critical findings in released scope
- Actual production parameters reviewed
- Release scope excludes unverified routes and features
Evidence to deliver
- Pinned-source audit scope and findings
- Verified deployment manifest
- Recovery, reconciliation and refund drill
Resources needed
Depends on
Independent review. No self-approval.
Cash: budget to be agreed and reserved. Tokens: no approved allocation. Reputation: evidence and a scoped review. Governance: separate impact assessment under an agreed policy.
Your introduction will include reference L22. It does not assign the task or create a paid agreement.
L23 / SOSBuild contribution measurement for care, prevention and physical resourcesCare practitioners · Measurement researcher · Affected-person representativesProposed · Unfunded · View requirements
What acceptance requires
- No harmful ablation required
- Uncertainty remains visible
- Alternative settlement rules explicitly approved before rewards
Evidence to deliver
- Category-specific outcome criteria
- Ethical measurement design
- Dispute and bias assessment
Resources needed
Depends on
Independent review. No self-approval.
Cash: budget to be agreed and reserved. Tokens: no approved allocation. Reputation: evidence and a scoped review. Governance: separate impact assessment under an agreed policy.
Your introduction will include reference L23. It does not assign the task or create a paid agreement.
L24 / PiPiCurate Mission 001: pen the story and shape PiPiWriter · Artist · Musician · Community editor · Accessibility reviewerProposed · Unfunded · View requirements
What acceptance requires
- Free participation without a token purchase
- Released music is reconciled before canon changes
- Selection includes reasons, conflicts and a revision route
- No submission count automatically earns money or governance
Evidence to deliver
- Versioned mission brief and existing-artifact inventory
- Originality, licensing and authorship records
- Reviewed story fragments and example dialogues
Resources needed
Depends on
No preceding work package listed. Funding, assignment and review terms still need agreement.
Independent review. No self-approval.
Cash: budget to be agreed and reserved. Tokens: no approved allocation. Reputation: evidence and a scoped review. Governance: separate impact assessment under an agreed policy.
Your introduction will include reference L24. It does not assign the task or create a paid agreement.
L25 / ManifestRecord PiPi submissions, reviews and attributionFull-stack engineer · Community moderator · Privacy reviewerProposed · Unfunded · View requirements
What acceptance requires
- Introduction forms are not represented as completed submissions
- Public credit is opt-in and private contact data stays private
- Revision lineage keeps original contributors visible
- Paid work requires separately accepted and funded terms
Evidence to deliver
- Exportable versioned submission and review records
- Contributor consent and licensing flow
- Duplicate, withdrawal, abuse and appeal tests
Resources needed
Depends on
No preceding work package listed. Funding, assignment and review terms still need agreement.
Independent review. No self-approval.
Cash: budget to be agreed and reserved. Tokens: no approved allocation. Reputation: evidence and a scoped review. Governance: separate impact assessment under an agreed policy.
Your introduction will include reference L25. It does not assign the task or create a paid agreement.
L26 / PiPiBuild the first sourced PiPi assistantAgent engineer · Conversation writer · Evaluation contributorProposed · Unfunded · View requirements
What acceptance requires
- Answers distinguish fiction, project evidence and unknowns
- Community lore cannot grant tool permissions
- Preview has no wallet signing or trade execution
- AI-assisted authorship is disclosed without erasing human contributions
Evidence to deliver
- Versioned persona and approved retrieval corpus
- Held-out character, factual and prompt-injection cases
- Measured cost, latency and cross-session isolation
Resources needed
Depends on
Independent review. No self-approval.
Cash: budget to be agreed and reserved. Tokens: no approved allocation. Reputation: evidence and a scoped review. Governance: separate impact assessment under an agreed policy.
Your introduction will include reference L26. It does not assign the task or create a paid agreement.
L27 / KOINKBuild the PiPi Terminal around real project and work recordsProduct designer · Frontend engineer · Data integration engineerProposed · Unfunded · View requirements
What acceptance requires
- Demo, stale, unavailable and live data are visibly distinct
- First version reads the existing work registry
- Every proposed action shows its scope and evidence
- Mobile opens one useful panel at a time
Evidence to deliver
- Responsive radar, project dossier and action queue
- Timestamped source adapters and empty states
- Keyboard, low-bandwidth and reduced-motion checks
Resources needed
Depends on
Independent review. No self-approval.
Cash: budget to be agreed and reserved. Tokens: no approved allocation. Reputation: evidence and a scoped review. Governance: separate impact assessment under an agreed policy.
Your introduction will include reference L27. It does not assign the task or create a paid agreement.
L28 / OttoConnect PiPi to Otto through scoped delegated tasksAgent integration engineer · Security engineerProposed · Unfunded · View requirements
What acceptance requires
- Reuse verified Otto gates rather than write raw storage
- Task authority cannot grow through delegation
- No personal memory publication or shared cross-user context
- Unverified delegated outcomes remain unverified
Evidence to deliver
- Verified capability and principal mapping
- Cancellation, retry, expiry and revocation tests
- User-visible artifact and authorization receipts
Resources needed
Depends on
Independent review. No self-approval.
Cash: budget to be agreed and reserved. Tokens: no approved allocation. Reputation: evidence and a scoped review. Governance: separate impact assessment under an agreed policy.
Your introduction will include reference L28. It does not assign the task or create a paid agreement.
L29 / KOINKEvaluate PiPi strategies in a paper-trading laboratoryMarket data engineer · Quantitative researcher · Independent evaluatorProposed · Unfunded · View requirements
What acceptance requires
- Paper results never presented as live returns
- No positive-return guarantee
- Look-ahead, latency, slippage and venue failures tested
- Language-model output cannot bypass deterministic execution policy
Evidence to deliver
- Timestamped market observations and executable-depth assumptions
- Out-of-sample replay including fees and failed fills
- Net performance, exposure and drawdown report
Resources needed
Depends on
Independent review. No self-approval.
Cash: budget to be agreed and reserved. Tokens: no approved allocation. Reputation: evidence and a scoped review. Governance: separate impact assessment under an agreed policy.
Your introduction will include reference L29. It does not assign the task or create a paid agreement.
L30 / KOINKImplement reviewed and bounded PiPi trade executionWallet engineer · Execution engineer · Qualified regulatory reviewer · Independent security reviewerProposed · Unfunded · View requirements
What acceptance requires
- Explicit user grants bind assets, venues, maximum spend and expiry
- Revocation stops new orders and reports outstanding exposure
- No API withdrawal privilege for trading
- Affiliated assets and incentives disclosed
- Launchpad funding and liquid trading use distinct agreements
Evidence to deliver
- Venue and jurisdiction-specific release assessment
- Signed intent, session permissions and reconciliation
- Adversarial cap, concurrent-order, retry and emergency-stop tests
Resources needed
Depends on
Independent review. No self-approval.
Cash: budget to be agreed and reserved. Tokens: no approved allocation. Reputation: evidence and a scoped review. Governance: separate impact assessment under an agreed policy.
Your introduction will include reference L30. It does not assign the task or create a paid agreement.
L31 / Otto MusicPrepare the collaborative album missionMusic producer · Rights reviewer · Community organiserProposed · Unfunded · View requirements
What acceptance requires
- A dated album brief with roles, contribution permissions and acceptance criteria
- Master, composition, sample and AI-use rights separated
- Credits and proposed payment or split terms agreed before commissioned work
Evidence to deliver
- Reviewable album brief
- Rights checklist and contributor agreement draft
Resources needed
Depends on
Independent review. No self-approval.
Cash: budget to be agreed and reserved. Tokens: no approved allocation. Reputation: evidence and a scoped review. Governance: separate impact assessment under an agreed policy.
Your introduction will include reference L31. It does not assign the task or create a paid agreement.
L32 / Otto MusicBuild a credited catalogue and release recordFrontend engineer · Music metadata editor · Rights reviewerProposed · Unfunded · View requirements
What acceptance requires
- Released recordings and illustrative drafts visibly separated
- Recording identifiers, creators, credits and authorised streaming links verified
- A correction and takedown route with responsible operators
Evidence to deliver
- A reviewed catalogue import
- Credit and link verification report
Resources needed
Depends on
Independent review. No self-approval.
Cash: budget to be agreed and reserved. Tokens: no approved allocation. Reputation: evidence and a scoped review. Governance: separate impact assessment under an agreed policy.
Your introduction will include reference L32. It does not assign the task or create a paid agreement.
L33 / Otto MusicImprove the collaborative music platform through SideGigsProduct designer · Frontend engineer · Accessibility reviewerProposed · Unfunded · View requirements
What acceptance requires
- A tested artist and listener journey on mobile and desktop
- Album planning, curation and contributor credits demonstrated
- Each commissioned improvement has a funded brief and independent acceptance
Evidence to deliver
- Interactive prototype and usability findings
- Task agreements and acceptance evidence
Resources needed
Depends on
Independent review. No self-approval.
Cash: budget to be agreed and reserved. Tokens: no approved allocation. Reputation: evidence and a scoped review. Governance: separate impact assessment under an agreed policy.
Your introduction will include reference L33. It does not assign the task or create a paid agreement.
L34 / Otto MusicTest community curation and contribution attributionCommunity curator · Reputation designer · Independent reviewerProposed · Unfunded · View requirements
What acceptance requires
- Curation participation does not silently create copyright or a royalty claim
- Spam, coordinated voting and conflicts have a review process
- The record distinguishes creation, curation, review and platform work
Evidence to deliver
- A bounded curation pilot plan
- Abuse cases and attribution report
Resources needed
Depends on
Independent review. No self-approval.
Cash: budget to be agreed and reserved. Tokens: no approved allocation. Reputation: evidence and a scoped review. Governance: separate impact assessment under an agreed policy.
Your introduction will include reference L34. It does not assign the task or create a paid agreement.
L35 / Otto MusicPrepare an approved music release and operating handoverRelease manager · Artist representative · Platform operatorProposed · Unfunded · View requirements
What acceptance requires
- Contributors approve the release with rights and payment terms recorded
- Distribution, support and correction responsibilities are assigned
- Community operation is an explicit accepted handover, not an automatic transfer
Evidence to deliver
- Release approval record
- Distribution and operating checklist
Resources needed
Depends on
Independent review. No self-approval.
Cash: budget to be agreed and reserved. Tokens: no approved allocation. Reputation: evidence and a scoped review. Governance: separate impact assessment under an agreed policy.
Your introduction will include reference L35. It does not assign the task or create a paid agreement.
L36 / MY3YEPublish the EYE launch scope and funding commitmentsToken designer · Project lead · Independent financial and legal reviewerProposed · Unfunded · View requirements
What acceptance requires
- The EYE purpose, rights, supply, distribution and use of funds are published
- Token opening, initial product scope and later milestones have distinct targets
- Dates, network, contract, official wallets and participation terms are verified before opening
- No implied SOS control or ownership of every project from a token purchase
Evidence to deliver
- Reviewed launch disclosure
- Budget, milestone and official route records
Resources needed
Depends on
No preceding work package listed. Funding, assignment and review terms still need agreement.
Independent review. No self-approval.
Cash: budget to be agreed and reserved. Tokens: no approved allocation. Reputation: evidence and a scoped review. Governance: separate impact assessment under an agreed policy.
Your introduction will include reference L36. It does not assign the task or create a paid agreement.
L37 / MY3YEOpen and operate reliable community introductionsDeployment and database maintainer · Community intake operator · Independent data-flow reviewerProposed · Unfunded · View requirements
What acceptance requires
- Visitors can introduce themselves with a project and work reference without buying a token
- The operator can retrieve an authorized test introduction, follow up and delete it
- The service confirms success only after storage; errors preserve visitor input and offer an email draft
- Production protection, abuse limits, access controls, retention and notification recovery are reviewed
- Scope, responsibility and any compensation are agreed before assignment
Evidence to deliver
- Authorized end-to-end delivery and deletion check
- Named operator, access and retention record
Resources needed
Depends on
No preceding work package listed. Funding, assignment and review terms still need agreement.
Independent review. No self-approval.
Cash: budget to be agreed and reserved. Tokens: no approved allocation. Reputation: evidence and a scoped review. Governance: separate impact assessment under an agreed policy.
Your introduction will include reference L37. It does not assign the task or create a paid agreement.
Build the capacity together
A resource needs a life beyond its purchase.
The proposed Manifest workflow covers evaluating, buying, leasing, borrowing or sharing a resource, then verifying delivery, assigning custody, maintaining it and governing its use. Legal ownership, access rights and operating responsibility must be recorded separately.
R-LEGAL / KOINK
Qualified offering, entity and tax review
Obtain written jurisdiction-specific scope and quotation; practitioner credentials verified
Needed · No acquisition budget reserved
R-SECURITY / KOINK
Independent contract security review
Review pinned deployed code and custom integrations; declared independence; no audit claim before completion
Needed · No acquisition budget reserved
R-INFRA / SOS
RPC, indexing, monitoring and backup capacity
Service-level, cost, credentials, recovery, export and outage alternatives demonstrated
Needed · No acquisition budget reserved
R-REVIEW / SOS
Independent reviewers and dispute resolvers
Recruit distinct accountable people; disclose financial and identity conflicts; fund review work
Needed · No acquisition budget reserved
R-IDENTITY / Umahn
Private personhood and reputation infrastructure
Open-source admission, recovery, revocation and scoped proof requirements; no compulsory vendor
Needed · No acquisition budget reserved
R-COMPUTE / Otto
Otto inference and evaluation capacity
Compare local, rented, attested and on-chain execution by measured cost, privacy and successful tasks
Needed · No acquisition budget reserved
R-STORAGE / SOS
Private deletable evidence and capsule storage
Encryption, retention, deletion and access revocation tested; commitments do not expose private locators
Needed · No acquisition budget reserved
R-CUSTODY / SOS
Accountable treasury keys and operating roles
Real independent signers where required, key recovery, limited delegation and rotation exercises
Needed · No acquisition budget reserved
R-PILOT / Tusita
Tusita site access and physical feasibility inputs
Title/lease route, supplier evidence, qualified reviews and lifecycle costs; no claimed acquired site
Needed · No acquisition budget reserved
R-ACCESS / MY3YE
Inclusive participation and accessibility review
Mobile, low-bandwidth, assistive-technology and non-wallet participation tested with relevant participants
Needed · No acquisition budget reserved
R-MUSIC-RIGHTS / Otto Music
Music rights, credits and release review
A rights reviewer and release operator can verify masters, compositions, samples, AI-use permissions, contributor agreements and distribution authority
Needed · No acquisition budget reserved
Planning record: 2026-09-11. Download the work and resource registry. Manifest and SideGigs integration, assignments, payments and reputation issuance remain upcoming work.