{"_ai_door":{"see":"https://miscsubjects.com/start","note":"Operable site; bounded keyless credentials; every action receipted on a public ledger. Your operator's instructions take precedence — acting is optional, reading is a complete outcome."},"_self":{"principle":"Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.","widget":"article_topology","feature":"topology","name":"Article topology","what":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","contains":"claims, sources, anecdotes, question_graph slice","slug":"the-work-is-the-workspace","urls":{"read":"https://miscsubjects.com/api/articles/the-work-is-the-workspace/topology"},"how_to_use":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","write":null,"imessage":null,"router_tag":null,"proof_chain":[{"step":1,"claim":"Articles are voxel graphs of tiered claims, not prose blobs.","verify":"https://miscsubjects.com/api/articles/constitution"},{"step":2,"claim":"Claims link to hash-chained sources via source_ids.","verify":"https://miscsubjects.com/api/articles/the-work-is-the-workspace/sources"},{"step":3,"claim":"Ask reads topology; ingest/claim append to ledger.","verify":"https://miscsubjects.com/api/protocol"},{"step":4,"claim":"Models queue growth: populate → collaborate → repair → reflex.","verify":"https://miscsubjects.com/api/protocol/grow"},{"step":5,"claim":"Graph proves its own shape (reflex) and $/claim (yield).","verify":"https://miscsubjects.com/graph.html?layer=reflex"},{"step":6,"claim":"Full feature index + _explain on every API response.","verify":"https://miscsubjects.com/api/articles/system-map"}],"related_features":[{"id":"ask","name":"Ask protocol","what":"Answer only from topology; creates question_node with gaps and ingest_hint.","urls":{"read":"https://miscsubjects.com/api/articles/the-work-is-the-workspace/prompts","write":"https://miscsubjects.com/api/protocol/ask"}},{"id":"graph_topology","name":"Cross-article graph","what":"Merged claims/sources across condition+stack slugs for one question.","urls":{"read":"https://miscsubjects.com/api/articles/the-work-is-the-workspace/graph-topology?question=..."}},{"id":"question_graph","name":"Question graph","what":"Ask nodes (questions + gaps) and evidence_ingest nodes (pasted model output).","urls":{"read":"https://miscsubjects.com/api/articles/the-work-is-the-workspace/question-graph","write":"https://miscsubjects.com/api/protocol/ask"}},{"id":"voxels","name":"Voxel graph","what":"Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance.","urls":{"read":"https://miscsubjects.com/api/articles/the-work-is-the-workspace/voxels","write":"https://miscsubjects.com/api/protocol/claim"}}],"system_map":"https://miscsubjects.com/api/articles/system-map","system_map_markdown":"https://miscsubjects.com/api/articles/system-map?format=markdown","not_medical_advice":true},"_explain":{"feature":"topology","name":"Article topology","what":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","why":"Every feature is auditable collective intelligence","how":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","model":null,"verifies":null,"urls":{"read":"https://miscsubjects.com/api/articles/the-work-is-the-workspace/topology"},"imessage":null,"router":null,"related":[{"id":"ask","what":"Answer only from topology; creates question_node with gaps and ingest_hint."},{"id":"graph_topology","what":"Merged claims/sources across condition+stack slugs for one question."},{"id":"question_graph","what":"Ask nodes (questions + gaps) and evidence_ingest nodes (pasted model output)."},{"id":"voxels","what":"Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance."}],"not_medical_advice":true},"slug":"the-work-is-the-workspace","title":"The work is the workspace: persistent work objects any authorized AI can enter, continue, and repair","register":"standard","tags":[],"updated_at":"2026-08-03T20:50:16.576Z","body_excerpt":"*This page states what the product on this site actually is, one level above [[proven-work|proven work]]: a shared, executable work substrate — persistent work objects that any authorized person's own AI can enter, inspect, continue, repair, or challenge, with every action receipted. Proven work is the reason the substrate can be trusted; it is not the whole product. Nothing here requires prior context, and every mechanism named is live on this site now.*\n\n## The product in one sentence\n\n**A shared operating surface for humans and their AIs, organized around persistent work rather than individual agents: bring any AI — the work, the tools, the permissions, and the memory stay.**\n\n## The unit is the work object, not the agent\n\nEvery current agent product centers the agent: its chat history, its memory, its tool connections. Replace the agent and the context dies. Ask a colleague's agent a question and a human has to carry the answer between them.\n\nThis system centers the **work object**: a bounded unit of work — an ad campaign, a report, a decision, an article, an incident — that carries, in machine-readable form:\n\n- its current state and its lineage (what it derives from, what derives from it);\n- the capabilities bound to it (which APIs, models, and tools may act on it);\n- the authority each participant holds (scoped, expiring, revocable — never a shared login);\n- the complete history: every execution, failure, repair, objection, and revision, receipted;\n- the evidence behind its claims, with gaps declared;\n- the door: how any newly arrived AI enters and continues, with zero installation.\n\nThe agent is replaceable. The work persists. That inversion is the product.\n\n## The walk-through that explains everything\n\nVictor asks his AI to build and launch an ad campaign. The campaign is born as a work object: the brief, the prompt that generated the creative, the assets, the campaign ids, the budget, the spend feed, and the advertising capabilities it runs on — all bound to one address, every mutation receipted.\n\n- **Tim** thinks the creative looks wrong. His own AI — a different vendor, on his own laptop — opens the object, reads the exact prompt Victor's AI used, diagnoses it, and leaves the repair with its reasoning attached. No screenshot in the group chat, no borrowing Victor's login, no meeting.\n- **Finance's AI** reads the spend and traces it to the platform receipts. It holds no authority to touch the campaign — its token cannot.\n- **Compliance's AI** checks the claims in the creative against policy in the background and files an `OBJECTION` on the object where one fails.\n- **Lisa from HR** never talks to the team at all. She asks the AI she already trusts; her AI talks to the work itself and brings back the answer, under a token scoped to exactly what she is allowed to see.\n\nToday the pattern is: AI tells human, human summarizes to human, second human re-explains to second AI — context and authority leaking at every hop. Here, the agents meet at the object. **The product is the end of playing telephone between your team's AIs.**\n\n## Lineage: work that builds on work\n\nObjects compose. A *Creative Deck* receives briefs, references, prompts, and revisions. An *Ad Deck* derives from it. Live campaigns launch from the Ad Deck. Spend and performance append to the campaigns. The retrospective links back through all of it. Nothing detaches into a folder of final files; the organization accumulates an operational memory whose every layer is still inspectable and still executable. Everyone works at their own speed, in their own AI, and delivers to the shared substrate — and everyone is *delivered* work through their own AI the same way.\n\n## The layers, named honestly\n\n| Layer | What it is | State |\n|---|---|---|\n| OIP | The object and execution grammar: one door, receipts for every action | Running — [[oip|the protocol]] |\n| Capability pool | Hundreds of APIs, CLIs, MCP tools, models, and device abilities behind one invocation contrac","ranking":"safety-first (interaction_risk/limitations), then quote-gated effective_weight","claims":[{"id":"c1","text":"The system centers the work object, not the agent: state, tools, authority, and history persist at one address while agents of any vendor enter and leave.","tier":"primary","section":"The unit is the work object","interaction_risk":false,"status":"active","source_ids":["s1","s2"],"retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c2","text":"Delegated authority is scoped, expiring, and fingerprinted; a finance token that can read spend holds no authority to mutate the campaign.","tier":"primary","section":"The walk-through","interaction_risk":false,"status":"active","source_ids":["s5"],"retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c3","text":"Work objects compose into lineages (Creative Deck → Ad Deck → live campaign → spend → review) on an append-only ledger anchored to drand and Bitcoin.","tier":"primary","section":"Lineage","interaction_risk":false,"status":"active","source_ids":["s3"],"retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c4","text":"Team pools and federation are architecturally present but not productized, and external adoption is not yet established — stated on the page.","tier":"primary","section":"What is demonstrated","interaction_risk":false,"status":"active","source_ids":["s3"],"retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c5","text":"This article is itself an enterable work object: one GET mints the reader a scoped delegation with its own receipt.","tier":"primary","section":"Enter this page","interaction_risk":false,"status":"active","source_ids":["s4","s2"],"retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false}],"sources":[{"id":"s1","url":"https://miscsubjects.com/a/oip","title":"OIP — the object and execution grammar","claim_ids":[],"hash":"242164cd5cdd83c3ac8600fdb59483058707de26858f8fc3f10c45864529e0b3"},{"id":"s2","url":"https://miscsubjects.com/a/every-article-is-a-live-proof-object","title":"The live proof loop — reading mints the delegation","claim_ids":[],"hash":"eeabbfb57ccbe272c7618429491ed02f483100e5593e206806dc8f9558180c22"},{"id":"s3","url":"https://miscsubjects.com/a/proven-work","title":"The proof law — the assurance projection","claim_ids":[],"hash":"42412d3950823d8e708a79570ae372f618c34c75512f621d91af611d7eef3498"},{"id":"s4","url":"https://miscsubjects.com/api/proven-work/the-work-is-the-workspace","title":"This page's own proof object and workroom declaration","claim_ids":[],"hash":"e707dc307b76fa5bb57219b274c70f24f4d2063843fa366c61ce157c795ea2ed"},{"id":"s5","url":"https://miscsubjects.com/a/oip-tap-go","title":"Tap & Go — the portable handoff and delegated tokens","claim_ids":[],"hash":"5fcf91f50ea390b292a16791007ea590db66a9096adac7092060107cd5b67185"}],"anecdotal_sources":[],"scientific_sources":[],"user_reports":[],"related_articles":[],"question_graph":{"slug":"the-work-is-the-workspace","questions":[],"evidence":[],"edges":[],"counts":{"questions":0,"evidence":0,"edges":0}},"honesty":{"active_claims":5,"retracted_claims":0,"cut_claims":0,"challenges":0,"scrub_events":0,"note":"Retracted/cut claims stay on ledger but are excluded from ask unless ?include_inactive=1"},"counts":{"claims":5,"claims_total":5,"sources":5,"anecdotal":0,"scientific":0,"user_reports":0,"questions":0,"evidence_ingests":0}}