{"aura-session-loop.c2c7e9b9f8":"or follow up","aura-session-loop.b10421a491":"this session","aura-session-loop.644b7c13c5":"recent, approvals","canonical-stack-overview.section.detail-label":"How to read the route","canonical-stack-overview.section.footer":"One request · explicit handoffs · evidence returned","canonical-stack-overview.visual.title":"A representative request path","canonical-stack-overview.visual.subtitle":"The route changes with the work. The identity, contracts, and return path stay explicit.","canonical-stack-overview.visual.status":"Return path intact","canonical-stack-overview.visual.meta":"8-product suite + Kera","canonical-stack-overview.visual.footer":"Only the layers a request needs have to run. This view shows the complete path so every boundary can be inspected.","canonical-stack-overview.journey.aria":"Six-stage path through the Dweve stack","canonical-stack-overview.journey.return":"result + evidence return to the work surface","canonical-stack-overview.packet.input.label":"Enters at the edge","canonical-stack-overview.packet.input.consumer.title":"Question or file","canonical-stack-overview.packet.input.consumer.body":"Your request and the context you choose to share","canonical-stack-overview.packet.input.business.title":"Objective packet","canonical-stack-overview.packet.input.business.body":"Objective, sources, policy, and accountable owner","canonical-stack-overview.packet.input.technical.title":"Typed request","canonical-stack-overview.packet.input.technical.body":"Pinned context, constraints, and declared output","canonical-stack-overview.packet.output.label":"Returns to the edge","canonical-stack-overview.packet.output.consumer.title":"Answer and record","canonical-stack-overview.packet.output.consumer.body":"A useful result with the reasons and sources that support it","canonical-stack-overview.packet.output.business.title":"Result and evidence","canonical-stack-overview.packet.output.business.body":"Decision-ready output, owner, approvals, and record","canonical-stack-overview.packet.output.technical.title":"Result and receipts","canonical-stack-overview.packet.output.technical.body":"Typed output, weave trace, permits, and execution receipt","canonical-stack-overview.stage.work.role":"Work surface","canonical-stack-overview.stage.work.artifact":"durable work object","canonical-stack-overview.stage.knowledge.role":"Governed knowledge","canonical-stack-overview.stage.knowledge.artifact":"governed source set","canonical-stack-overview.stage.cognition.role":"Woven cognition","canonical-stack-overview.stage.cognition.artifact":"result + weave trace","canonical-stack-overview.stage.coordination.role":"Governed action","canonical-stack-overview.stage.coordination.artifact":"authorised task plan","canonical-stack-overview.stage.compute.role":"Compute","canonical-stack-overview.stage.compute.artifact":"executable plan","canonical-stack-overview.stage.placement.role":"Placement","canonical-stack-overview.stage.placement.artifact":"signed execution receipt","canonical-stack-overview.kera.label":"Separate foundation · when selected","canonical-stack-overview.kera.body":"graph-native language and toolchain","canonical-stack-overview.relationships.eyebrow":"Verified foundations","canonical-stack-overview.relationships.title":"The products do not hide what they depend on","canonical-stack-overview.relationships.boundary":"Only relationships asserted by the current product and open-source pages are drawn here. Absence from this ledger is not a claim that a foundation is unused.","canonical-stack-overview.relationships.built-on":"Built on","canonical-stack-overview.relationships.built-on-definition":"Inside the product or a real dependency of it.","canonical-stack-overview.relationships.works-with":"Works with","canonical-stack-overview.relationships.works-with-definition":"A supported integration, not an internal dependency.","canonical-stack-overview.relationships.research":"Research","canonical-stack-overview.relationships.independent-title":"Foundations with no product edge asserted in this view","canonical-stack-overview.relationships.independent-body":"Numerus, Signum, and Selvedge remain part of the 14 open-source routes. This ledger does not invent a product relationship where the current pages do not make one.","canonical-stack-overview.instrument.status":"Traceable","canonical-stack-overview.instrument.meta.scope":"Scope","canonical-stack-overview.instrument.meta.scope-value":"one request","canonical-stack-overview.instrument.meta.mode":"Route","canonical-stack-overview.instrument.meta.mode-value":"need-led","canonical-stack-overview.instrument.footer":"The route may shorten. The thread must not break.","canonical-stack-overview.instrument.row.identity.label":"Identity","canonical-stack-overview.instrument.row.boundary.label":"Boundary","canonical-stack-overview.instrument.row.return.label":"Return","canonical-stack-overview.instrument.consumer.title":"What stays attached","canonical-stack-overview.instrument.consumer.subtitle":"The answer should never become detached from the request.","canonical-stack-overview.instrument.consumer.identity":"Your question remains the thread through the run.","canonical-stack-overview.instrument.consumer.boundary":"Each handoff says what moves and what stays private.","canonical-stack-overview.instrument.consumer.return":"The result comes back with reasons and sources.","canonical-stack-overview.instrument.business.title":"The thread that stays intact","canonical-stack-overview.instrument.business.subtitle":"Accountability travels with the work.","canonical-stack-overview.instrument.business.identity":"The objective, owner, and source set retain one identity.","canonical-stack-overview.instrument.business.boundary":"Policy and approval gates remain named at every handoff.","canonical-stack-overview.instrument.business.return":"The result returns with evidence, decisions, and ownership.","canonical-stack-overview.instrument.technical.title":"The invariant through the run","canonical-stack-overview.instrument.technical.subtitle":"Contracts preserve identity across replaceable components.","canonical-stack-overview.instrument.technical.identity":"The request ID and pinned inputs follow every derived artifact.","canonical-stack-overview.instrument.technical.boundary":"Typed handoffs expose policy, execution, and placement decisions.","canonical-stack-overview.instrument.technical.return":"Trace and receipts join the typed result at the caller.","canonical-stack-overview.surface.stack.consumer.eyebrow":"The stack in motion","canonical-stack-overview.surface.stack.consumer.headline-lead":"One request keeps its identity","canonical-stack-overview.surface.stack.consumer.headline-accent":"from question to evidence","canonical-stack-overview.surface.stack.consumer.body":"The stack is easiest to understand as a journey. A question enters once, crosses only the boundaries it needs, and comes back with a result you can inspect. The labels keep product, foundation and research status separate before you choose a route.","canonical-stack-overview.surface.stack.consumer.detail-left":"The named stages show who owns knowledge, reasoning, action, compute and placement, so at every step you can see which owner answers and where the question stops if the later stages are never needed.","canonical-stack-overview.surface.stack.consumer.detail-right":"A request crosses only the boundaries it needs, so the full route is a map of what can happen rather than a promise that every product runs on every question, and the product, foundation and research labels stay separate as you read it.","canonical-stack-overview.surface.stack.business.eyebrow":"The stack in motion","canonical-stack-overview.surface.stack.business.headline-lead":"One request keeps its identity","canonical-stack-overview.surface.stack.business.headline-accent":"from objective to evidence","canonical-stack-overview.surface.stack.business.body":"The stack is one accountable operating path, not a catalogue of disconnected tools. An objective enters with its owner, sources, and policy, then returns as a result with evidence. That separation keeps the commercial scope legible while the route remains flexible.","canonical-stack-overview.surface.stack.business.detail-left":"Each product owns a distinct responsibility, so a team can adopt the layer that matches its operating need without taking on the whole path, and the boundary it buys stays legible in the commercial scope.","canonical-stack-overview.surface.stack.business.detail-right":"Only the required layers run, and explicit handoffs keep approvals, sources and execution records attached to the original objective, so the evidence returns with the result instead of being reassembled afterwards.","canonical-stack-overview.surface.stack.technical.eyebrow":"The stack in motion","canonical-stack-overview.surface.stack.technical.headline-lead":"One request keeps its identity","canonical-stack-overview.surface.stack.technical.headline-accent":"from typed input to receipts","canonical-stack-overview.surface.stack.technical.body":"Read the architecture as a request path. Typed input becomes governed context, a traceable result, an authorised plan, an executable plan, and a placement receipt. The route is descriptive: it records contracts and evidence, not a mandatory call graph.","canonical-stack-overview.surface.stack.technical.detail-left":"Named contracts keep components replaceable without hiding what each handoff accepts or emits, so a substitution stays reviewable and the schema at the boundary remains the thing actually under review.","canonical-stack-overview.surface.stack.technical.detail-right":"A route can skip unneeded responsibilities while preserving request identity, pinned inputs, permits and the return trace, so a shorter path is still a fully accounted one and every crossing it does make stays typed.","canonical-stack-overview.surface.products.consumer.eyebrow":"Why these products connect","canonical-stack-overview.surface.products.consumer.headline-lead":"Each product owns one part","canonical-stack-overview.surface.products.consumer.headline-accent":"of the same request","canonical-stack-overview.surface.products.consumer.body":"You can start with one product. When a request needs more, the products pass it forward without losing the question, sources, or record.","canonical-stack-overview.surface.products.consumer.detail-left":"The eight-product suite spans the work surface, knowledge, reasoning, governed action, compute, and placement. Each one owns a single part of the request, so you can start with the part you recognise and add the rest only when a request actually needs it.","canonical-stack-overview.surface.products.consumer.detail-right":"Kera is a separate systems foundation, selected only when that graph-native route is the right fit. It is not a ninth part of the suite, so you can read the eight products as one set and treat Kera as the route underneath, chosen for its own reasons.","canonical-stack-overview.surface.products.business.eyebrow":"Why these products form a stack","canonical-stack-overview.surface.products.business.headline-lead":"Each product owns one part","canonical-stack-overview.surface.products.business.headline-accent":"of the same run","canonical-stack-overview.surface.products.business.body":"Buy for the responsibility you need first. The suite can then connect work, governed knowledge, reasoning, coordination, compute, and placement without turning one operation into eight projects.","canonical-stack-overview.surface.products.business.detail-left":"The eight suite products can operate as one system, with each product carrying a named commercial responsibility. Buy the responsibility you need first and connect the rest later, so a first purchase stays scoped to one named owner rather than to the whole suite.","canonical-stack-overview.surface.products.business.detail-right":"Kera remains a separate systems language and toolchain, rather than a ninth component in the suite. It is selected when that graph-native route fits, and it is never a required step, so the licensed suite still counts eight products and nothing more.","canonical-stack-overview.surface.products.technical.eyebrow":"Why these products form a stack","canonical-stack-overview.surface.products.technical.headline-lead":"Each product owns one contract","canonical-stack-overview.surface.products.technical.headline-accent":"in the same request path","canonical-stack-overview.surface.products.technical.body":"The products divide responsibility without hiding the handoffs. Start at any contract boundary, adopt the components you need, and keep the caller-facing result inspectable.","canonical-stack-overview.surface.products.technical.detail-left":"The suite spans interface, knowledge, cognition, coordination, compute, and placement through named contracts. Each boundary is typed, so a component can be replaced without rewriting its neighbours.","canonical-stack-overview.surface.products.technical.detail-right":"Kera is a separate graph-native systems language and toolchain that participates only when selected. The request path does not require it, so the eight contracts hold without it and a route can be read end to end from the suite alone.","canonical-stack-overview.surface.see-it-work.consumer.eyebrow":"See the whole run","canonical-stack-overview.surface.see-it-work.consumer.headline-lead":"Watch the request move","canonical-stack-overview.surface.see-it-work.consumer.headline-accent":"then inspect what comes back","canonical-stack-overview.surface.see-it-work.consumer.body":"A useful demonstration should show more than the answer. Follow the request through the work it needs, then inspect the record returned with the result. The map below traces one request from the moment it is asked to the moment it comes back, naming what it read, what it decided, and what it left behind.","canonical-stack-overview.surface.see-it-work.consumer.detail-left":"The demonstration below follows one concrete run from request to result, so the visible artefacts have a clear origin.","canonical-stack-overview.surface.see-it-work.consumer.detail-right":"This wider map shows where sources, decisions, execution, and evidence sit around that run.","canonical-stack-overview.surface.see-it-work.business.eyebrow":"See the whole run","canonical-stack-overview.surface.see-it-work.business.headline-lead":"Watch the request move","canonical-stack-overview.surface.see-it-work.business.headline-accent":"then inspect what comes back","canonical-stack-overview.surface.see-it-work.business.body":"Do not judge the system from a polished answer alone. Follow the objective, owner, sources, policy, approvals, execution, and evidence as one accountable run. Each stage leaves an artefact you can name and an owner you can ask, and the map below shows where each one sits on the route your own request would take.","canonical-stack-overview.surface.see-it-work.business.detail-left":"The concrete demonstration zooms in on a single accountable route, with each artefact tied to the responsibility that produced it.","canonical-stack-overview.surface.see-it-work.business.detail-right":"Use the wider map to check what should return to the operating record and who owns that handoff.","canonical-stack-overview.surface.see-it-work.technical.eyebrow":"See the whole run","canonical-stack-overview.surface.see-it-work.technical.headline-lead":"Watch the request move","canonical-stack-overview.surface.see-it-work.technical.headline-accent":"then inspect every receipt","canonical-stack-overview.surface.see-it-work.technical.body":"A demo is only useful when the boundary artifacts are visible. Follow the typed request through context, trace, permits, execution, and placement, then reproduce the returned evidence. Each boundary below names what the component accepted, what it emitted, and what it preserved, so the pack replays against the same route.","canonical-stack-overview.surface.see-it-work.technical.detail-left":"The run below is the concrete test: inspect what each component accepted, emitted, and preserved at its boundary.","canonical-stack-overview.surface.see-it-work.technical.detail-right":"The route is the reference model for reproducing the returned trace, permits, execution, and placement evidence.","canonical-stack-overview.surface.home.consumer.eyebrow":"One connected path","canonical-stack-overview.surface.home.consumer.headline-lead":"Your request remains yours","canonical-stack-overview.surface.home.consumer.headline-accent":"all the way back","canonical-stack-overview.surface.home.consumer.body":"A question should not disappear into a black box. It should come back as a useful answer with a record you can understand.","canonical-stack-overview.surface.home.consumer.detail-left":"The route shows where knowledge, reasoning, action, and execution fit around your question.","canonical-stack-overview.surface.home.consumer.detail-right":"Most requests use only part of it, so the map explains the shape without prescribing a fixed journey.","canonical-stack-overview.surface.home.business.eyebrow":"From operation to accountable result","canonical-stack-overview.surface.home.business.headline-lead":"One operation on one stack","canonical-stack-overview.surface.home.business.headline-accent":"not eight projects","canonical-stack-overview.surface.home.business.body":"Start with an objective, its owner, sources, and policy. The stack coordinates the responsibilities it needs and returns the result, approvals, evidence, and record to the work surface.","canonical-stack-overview.surface.home.business.detail-left":"Each product can stand on its own, with a responsibility that remains clear when the operating path grows. An objective, its owner, its sources, and its policy are named at the start rather than assembled later.","canonical-stack-overview.surface.home.business.detail-right":"Together, explicit handoffs extend one path without rebuilding identity, governance, or evidence at every layer. The result, approvals, evidence, and record come back to the same work surface the request left from.","canonical-stack-overview.surface.home.technical.eyebrow":"Canonical request path","canonical-stack-overview.surface.home.technical.headline-lead":"The request is the thread","canonical-stack-overview.surface.home.technical.headline-accent":"and every handoff is visible","canonical-stack-overview.surface.home.technical.body":"A typed request carries pinned context through governed knowledge, woven cognition, authorised coordination, compute, and placement. The caller gets the result and the evidence chain together.","canonical-stack-overview.surface.home.technical.detail-left":"The architecture is composable rather than mandatory end to end; only the required responsibilities run. A typed request carries its pinned context into knowledge, cognition, coordination, compute, and placement only where those are needed.","canonical-stack-overview.surface.home.technical.detail-right":"Their contracts preserve request identity, declared boundaries, and reproducible return artefacts for the caller. The result and the evidence chain arrive together, so the caller does not have to reassemble one from the other.","core-extras.96d330537a":"Base IR","core-extras.bee831a169":"Substrate","core-extras.61a0822826":"Apps on Core","core-extras.15438cc098":"not supported","core-extras.ad565d9d01":"Feature","core-extras.0155bf03e5":"Segment legend","core-extras.8b7110078e":"Algorithm groups by data type","core-extras.25ab4276a6":"Scrollable capability matrix","home-page.hero.consumer.eyebrow":"Your everyday workspace","home-page.hero.consumer.title.0":"Turn what you have","home-page.hero.consumer.title.1":"into something useful","home-page.hero.consumer.lede":"Fabric brings your questions, files, notes, links, mail, and calendar context into one private workspace. Ask in everyday language, inspect the sources behind an answer, and turn the work you repeat into a routine you can keep using.","home-page.hero.consumer.action.primary":"See Fabric at work","home-page.hero.consumer.action.secondary":"Follow one answer","home-page.hero.consumer.ledger.label":"Inside Fabric","home-page.hero.consumer.ledger.pill":"Public Mesh","home-page.hero.consumer.ledger.row.0.label":"Your question","home-page.hero.consumer.ledger.row.0.value":"Ask in your own words","home-page.hero.consumer.ledger.row.1.label":"Your context","home-page.hero.consumer.ledger.row.1.value":"Files and notes stay together","home-page.hero.consumer.ledger.row.2.label":"Your answer","home-page.hero.consumer.ledger.row.2.value":"Open the sources it used","home-page.hero.consumer.ledger.row.3.label":"Your control","home-page.hero.consumer.ledger.row.3.value":"Correct, share, export, or remove","home-page.hero.consumer.ledger.caption":"One workspace for your context, answers, and recurring work.","home-page.hero.business.eyebrow":"For operations and finance","home-page.hero.business.title.0":"Move decisions faster","home-page.hero.business.title.1":"without losing control","home-page.hero.business.lede":"Dweve turns document-heavy work into a controlled flow from intake to approval. Sources, policy checks, exceptions, owners, actions, and evidence stay in one record, so operations can clear blockers and finance can measure the gain before scaling.","home-page.hero.business.action.primary":"Prove one workflow","home-page.hero.business.action.secondary":"See the rollout","home-page.hero.business.ledger.label":"Operating gain","home-page.hero.business.ledger.pill":"Measured in flow","home-page.hero.business.ledger.row.0.label":"Throughput","home-page.hero.business.ledger.row.0.value":"Less waiting and repeat review","home-page.hero.business.ledger.row.1.label":"Control","home-page.hero.business.ledger.row.1.value":"Owners and approval gates named","home-page.hero.business.ledger.row.2.label":"Evidence","home-page.hero.business.ledger.row.2.value":"Built while the work moves","home-page.hero.business.ledger.row.3.label":"Spend","home-page.hero.business.ledger.row.3.value":"Use the estate before adding capacity","home-page.hero.business.ledger.caption":"Baseline one workflow, run real work, and compare the result.","home-page.hero.technical.eyebrow":"For engineers and scientists","home-page.hero.technical.title.0":"Trace the request","home-page.hero.technical.title.1":"through every boundary","home-page.hero.technical.lede":"A request begins as a durable Fabric object and invokes only the product boundaries the work needs. Agent, cognition, knowledge, policy, target, execution, and placement events return with the result, each tied to a named contract.","home-page.hero.technical.ledeSecondary":"Inspect the representations, constraints, computation, placement, and claim boundaries instead of trusting a model name.","home-page.hero.technical.action.primary":"Follow the trace","home-page.hero.technical.action.secondary":"Inspect the foundations","home-page.hero.technical.ledger.label":"Architecture","home-page.hero.technical.ledger.pill":"OPEN FOUNDATIONS","home-page.hero.technical.ledger.row.0.label":"Typed contracts","home-page.hero.technical.ledger.row.0.value":"APIs, ABIs, portable formats","home-page.hero.technical.ledger.row.1.label":"Cognitive graphs","home-page.hero.technical.ledger.row.1.value":"Typed specialist routes","home-page.hero.technical.ledger.row.2.label":"Versioned knowledge","home-page.hero.technical.ledger.row.2.value":"Atoms, versions, lineage","home-page.hero.technical.ledger.row.3.label":"Hard replay","home-page.hero.technical.ledger.row.3.value":"Bit-exact on fixed seed","home-page.hero.technical.ledger.row.4.label":"Topology","home-page.hero.technical.ledger.row.4.value":"Managed Mesh, licensed, or air-gapped","home-page.hero.technical.ledger.caption":"Start at the trace, the responsibility map, or a computation contract.","home-page.cta.consumer.eyebrow":"Early access","home-page.cta.consumer.title":"Reserve your place in Fabric","home-page.cta.consumer.body":"Pre-order Fabric Personal for EUR 14.25 or Fabric Friends & Family for EUR 35.63 for five named people. The pre-order price remains fixed for the uninterrupted contract. Access opens by group; it is not public yet.","home-page.cta.consumer.action.primary":"Pre-order Fabric","home-page.cta.consumer.action.secondary":"Read the access terms","home-page.cta.business.eyebrow":"Next step","home-page.cta.business.title":"Prove gain on one workflow","home-page.cta.business.body":"Choose real work with a known baseline, real documents, a named owner, and an approval. Compare cycle time, queue age, repeat work, exceptions, and evidence effort before deciding how far to expand.","home-page.cta.business.action.primary":"Start the proof","home-page.cta.business.action.secondary":"Plan deployment","home-page.cta.technical.eyebrow":"Inspect the system","home-page.cta.technical.title":"Start with the boundary you doubt most","home-page.cta.technical.body":"Follow a request trace, inspect the system map, or test a handoff at the knowledge, policy, execution, or placement boundary. Judge the architecture by the state and evidence it returns.","home-page.cta.technical.action.primary":"Read the system map","home-page.cta.technical.action.secondary":"Follow the trace","home-page.faq.q0":"What is Fabric?","home-page.faq.a0":"Your personal Fabric interface. Chat with memory, upload files, build small assistants, and save recurring routines through the public Dweve Mesh.","home-page.faq.q1":"Does Fabric train on my data?","home-page.faq.a1":"No. Your conversations and files stay yours. We do not train models on your content, ever.","home-page.faq.q2":"Where does my data live?","home-page.faq.a2":"In the EU only. The Business Workspace uses EU-only paths on the public Dweve Mesh, so your data is not routed through other jurisdictions.","home-page.faq.q3":"What does it cost?","home-page.faq.a3":"Fabric Personal is EUR 19 a month for one named person. Fabric Friends & Family is EUR 47.50 for five named people, the price of 2.5 Personal subscriptions. Both use Fabric through the web and app without Aura, direct API access or Agent SDK rights. The compute-contribution route is limited to eligible Personal customers after the first paid month.","home-page.faq.status":"ANSWERED","home-page.faq.q4":"Can I see how it reached an answer?","home-page.faq.a4":"Yes. Every answer shows where it came from. You can open the sources behind any response instead of taking it on faith.","home-page.5adc21c02d":"REAL ASKS","home-page.d08b22d497":"letter-1957-04-12.jpg","home-page.f4d8b462e8":"letter-1957-05-02.jpg","home-page.781cfbbb75":"FABRIC","home-page.ea7792a26f":"context","home-page.2f2fc7f2e9":"ask","home-page.a39a7ffad4":"assistant","home-page.e778bd0f47":"CONNECTORS","home-page.1dabba21cd":"✓","home-page.eca5cf72fe":"3 counts","home-page.c1f8db4b1c":"PRICING","home-page.0e7d6a4fb2":"Month one","home-page.5bf4a92fb6":"Your choice","home-page.4d1ca74fb7":"Where it goes","home-page.cta.consumer.titleLead":"Reserve your place","home-page.cta.consumer.titleAccent":"in Fabric","home-page.cta.business.titleLead":"Prove gain","home-page.cta.business.titleAccent":"on one workflow","home-page.cta.technical.titleLead":"Start with the boundary","home-page.cta.technical.titleAccent":"you doubt most","home-page.b83e2d32a6":"Bring your mail, your calendar, your files, and the apps you use every day into one place, so Fabric can work with what is already there instead of starting from a black box.","home-page.fbf1f7f22d":"Personal is EUR 19 a month and Friends & Family is EUR 47.50 for five named people. Their pre-order prices are EUR 14.25 and EUR 35.63. Both are billed by a Dutch entity and cancelable at any time. After the first paid month, an eligible individual Personal customer may instead use the compute-contribution route; Friends & Family is excluded.","home-page.ec12d38b37":"Trust & deployment","home-page.8f4bc24f4a":"Built for ","home-page.31a077bcd6":"Europe.","home-page.45fdad31c3":"Sovereign AI with clear deployment options.","home-page.c257c8e65a":"managed Mesh","home-page.6a8ecf41d8":"Where Dweve runs","home-page.78df88e104":"EU regions","home-page.3e2947d435":"Jurisdiction aware","home-page.2e0bea60f4":"Node routing","home-page.87d635c3e6":"Business Workspace","home-page.d40f6e5b92":"European infrastructure under European law.","home-page.f6c82c9b8c":"Licensed","home-page.80880cf48a":"Private, on-prem, or air-gapped environments.","home-page.9704978b3c":"Trust model","home-page.24dd583e20":"Data control","home-page.9e504d2d2b":"Auditability","home-page.34cdb798b2":"Predictable posture","home-page.cecff0525a":"Vendor clarity","home-page.95c0386d8a":"Community path","home-page.e7679b83e8":"After the first paid month, eligible customers may use Fabric's published spare-compute route under its current terms.","home-page.ca4d98a9aa":"EU jurisdiction, controlled deployment, no sovereignty asterisks","home-page.rework.business.opening.eyebrow":"The work behind the decision","home-page.rework.business.opening.title.0":"Start with the work","home-page.rework.business.opening.title.1":"not the platform","home-page.rework.business.opening.body":"A useful system takes the messy part seriously: the documents, people, rules, and hand-offs that surround a decision. Dweve brings them into one review path so a team can move from a question to an answer that has an owner and a next step.","home-page.rework.business.opening.pill.0":"Real documents","home-page.rework.business.opening.pill.1":"Named owners","home-page.rework.business.opening.pill.2":"Reviewable outcomes","home-page.rework.business.opening.side.label":"What changes","home-page.rework.business.opening.side.pill":"FIRST WORKFLOW","home-page.rework.business.opening.side.0.label":"The question","home-page.rework.business.opening.side.0.value":"Stops living in a queue","home-page.rework.business.opening.side.1.label":"The evidence","home-page.rework.business.opening.side.1.value":"Arrives with the answer","home-page.rework.business.opening.side.2.label":"The owner","home-page.rework.business.opening.side.2.value":"Sees what needs a call","home-page.rework.business.opening.side.3.label":"The record","home-page.rework.business.opening.side.3.value":"Is ready when work closes","home-page.rework.business.opening.visual.header":"Decision workspace","home-page.rework.business.opening.visual.status":"READY FOR REVIEW","home-page.rework.business.opening.visual.stage.0.label":"INTAKE","home-page.rework.business.opening.visual.stage.0.title":"Collect the ask","home-page.rework.business.opening.visual.stage.0.body":"Question, files, deadline","home-page.rework.business.opening.visual.stage.1.label":"GROUND","home-page.rework.business.opening.visual.stage.1.title":"Find the rule","home-page.rework.business.opening.visual.stage.1.body":"Policy, contract, precedent","home-page.rework.business.opening.visual.stage.2.label":"REVIEW","home-page.rework.business.opening.visual.stage.2.title":"Show the difference","home-page.rework.business.opening.visual.stage.2.body":"Conflict, exception, risk","home-page.rework.business.opening.visual.stage.3.label":"DECIDE","home-page.rework.business.opening.visual.stage.3.title":"Give someone a call","home-page.rework.business.opening.visual.stage.3.body":"Approve, return, escalate","home-page.rework.business.opening.visual.result":"The answer is useful because the next action is clear","home-page.rework.business.control.eyebrow":"A better operating rhythm","home-page.rework.business.control.title.0":"Make the reasoning visible","home-page.rework.business.control.title.1":"before the meeting","home-page.rework.business.control.body":"Dweve does not replace judgement. It prepares the ground for it: the relevant material is gathered, the open points are surfaced, and the proposed answer can be challenged before it becomes a commitment.","home-page.rework.business.control.pill.0":"Sources beside claims","home-page.rework.business.control.pill.1":"Exceptions highlighted","home-page.rework.business.control.pill.2":"Approval stays human","home-page.rework.business.control.side.label":"The manager view","home-page.rework.business.control.side.pill":"DECISION RECORD","home-page.rework.business.control.side.0.label":"What is known","home-page.rework.business.control.side.0.value":"Source-backed","home-page.rework.business.control.side.1.label":"What is missing","home-page.rework.business.control.side.1.value":"Named before approval","home-page.rework.business.control.side.2.label":"What changed","home-page.rework.business.control.side.2.value":"Visible in the thread","home-page.rework.business.control.side.3.label":"What happens next","home-page.rework.business.control.side.3.value":"Assigned, not implied","home-page.rework.business.control.visual.header":"Review record","home-page.rework.business.control.visual.status":"OPEN DECISION","home-page.rework.business.control.visual.questionLabel":"QUESTION","home-page.rework.business.control.visual.answerLabel":"PROPOSED ANSWER","home-page.rework.business.control.visual.action.return":"RETURN TO OWNER","home-page.rework.business.control.visual.action.approve":"APPROVE","home-page.rework.business.control.visual.action.change":"REQUEST CHANGE","home-page.rework.business.control.visual.prompt":"Can this supplier handle the new data boundary?","home-page.rework.business.control.visual.answer":"The contract covers retention, but the incident clause needs an owner before sign-off.","home-page.rework.business.control.visual.source.0":"vendor-contract-v4.pdf","home-page.rework.business.control.visual.source.1":"dora-risk-register.pdf","home-page.rework.business.control.visual.source.2":"security-addendum.docx","home-page.rework.business.control.visual.footer":"RETURN TO OWNER  ·  2 OPEN POINTS  ·  REVIEWABLE","home-page.rework.business.deployment.eyebrow":"Control that fits the operation","home-page.rework.business.deployment.title.0":"Choose where the work runs","home-page.rework.business.deployment.title.1":"without changing the work","home-page.rework.business.deployment.body":"Start in a European region, move the same workflow into your own environment, or isolate it completely. The operating model changes; the way people review and approve work does not.","home-page.rework.business.deployment.pill.0":"Managed Mesh","home-page.rework.business.deployment.pill.1":"Private deployment","home-page.rework.business.deployment.pill.2":"Air-gapped when needed","home-page.rework.business.deployment.side.label":"Deployment choices","home-page.rework.business.deployment.side.pill":"YOUR BOUNDARY","home-page.rework.business.deployment.side.0.label":"Business Workspace","home-page.rework.business.deployment.side.0.value":"EU region, managed","home-page.rework.business.deployment.side.1.label":"Private","home-page.rework.business.deployment.side.1.value":"Your network, your policy","home-page.rework.business.deployment.side.2.label":"Isolated","home-page.rework.business.deployment.side.2.value":"No outbound path","home-page.rework.business.deployment.side.3.label":"Evidence","home-page.rework.business.deployment.side.3.value":"Travels with the work","home-page.rework.business.deployment.visual.header":"Same workflow, three boundaries","home-page.rework.business.deployment.visual.status":"BOUNDARY SELECTED","home-page.rework.business.deployment.visual.path.question":"QUESTION","home-page.rework.business.deployment.visual.path.sources":"SOURCES","home-page.rework.business.deployment.visual.path.decision":"DECISION","home-page.rework.business.deployment.visual.selected":"SELECTED","home-page.rework.business.deployment.visual.available":"AVAILABLE","home-page.rework.business.deployment.visual.hosted":"MANAGED MESH","home-page.rework.business.deployment.visual.private":"PRIVATE","home-page.rework.business.deployment.visual.isolated":"ISOLATED","home-page.rework.business.deployment.visual.caption":"The decision path stays familiar while the data boundary follows your risk posture","home-page.rework.technical.runtime.eyebrow":"Read the request path","home-page.rework.technical.runtime.title.0":"Make the runtime visible","home-page.rework.technical.runtime.title.1":"then judge the claim","home-page.rework.technical.runtime.body":"A model name is not an architecture. The useful question is what happens between input and output: which representation is chosen, which constraints fire, what is retained, and what can be replayed later.","home-page.rework.technical.runtime.pill.0":"Typed input","home-page.rework.technical.runtime.pill.1":"Explicit route","home-page.rework.technical.runtime.pill.2":"Replayable result","home-page.rework.technical.runtime.side.label":"Runtime contract","home-page.rework.technical.runtime.side.pill":"TRACE READY","home-page.rework.technical.runtime.side.0.label":"Input","home-page.rework.technical.runtime.side.0.value":"Normalised once","home-page.rework.technical.runtime.side.1.label":"Route","home-page.rework.technical.runtime.side.1.value":"Selected by constraint","home-page.rework.technical.runtime.side.2.label":"Result","home-page.rework.technical.runtime.side.2.value":"Carries its evidence","home-page.rework.technical.runtime.side.3.label":"Replay","home-page.rework.technical.runtime.side.3.value":"Same input, same path","home-page.rework.technical.runtime.visual.header":"request trace","home-page.rework.technical.runtime.visual.status":"REPLAYABLE","home-page.rework.technical.runtime.visual.live":"LIVE","home-page.rework.technical.runtime.visual.row.0":"input    document + policy","home-page.rework.technical.runtime.visual.row.1":"parse    typed fields","home-page.rework.technical.runtime.visual.row.2":"route    constraint match","home-page.rework.technical.runtime.visual.row.3":"infer    binary state","home-page.rework.technical.runtime.visual.row.4":"prove    evidence bundle","home-page.rework.technical.runtime.visual.row.5":"return   answer + receipt","home-page.rework.technical.runtime.visual.footer":"TRACE COMPLETE  ·  0 UNEXPLAINED HOPS  ·  READY TO REPLAY","home-page.rework.technical.stack.eyebrow":"The layers underneath","home-page.rework.technical.stack.title.0":"Keep the boundaries explicit","home-page.rework.technical.stack.title.1":"so the system stays changeable","home-page.rework.technical.stack.body":"The stack is split where a team needs to make a different decision: arithmetic, representation, policy, runtime, and product surface. Each layer has a job, an interface, and a reason to exist.","home-page.rework.technical.stack.pill.0":"Small contracts","home-page.rework.technical.stack.pill.1":"Replaceable surfaces","home-page.rework.technical.stack.pill.2":"No mystery layer","home-page.rework.technical.stack.side.label":"Boundary map","home-page.rework.technical.stack.side.pill":"SYSTEM SHAPE","home-page.rework.technical.stack.side.0.label":"Numerics","home-page.rework.technical.stack.side.0.value":"Stable arithmetic","home-page.rework.technical.stack.side.1.label":"Meaning","home-page.rework.technical.stack.side.1.value":"Composable state","home-page.rework.technical.stack.side.2.label":"Runtime","home-page.rework.technical.stack.side.2.value":"Policy and execution","home-page.rework.technical.stack.side.3.label":"Surface","home-page.rework.technical.stack.side.3.value":"Products and tools","home-page.rework.technical.stack.visual.header":"system boundaries","home-page.rework.technical.stack.visual.layer.0":"PRODUCTS     Fabric · Mesh · Spindle","home-page.rework.technical.stack.visual.layer.1":"RUNTIME     Kera · Core · Loom","home-page.rework.technical.stack.visual.layer.2":"PROOF       AION · Ledger · Selvedge","home-page.rework.technical.stack.visual.layer.3":"MEANING     BitWeave · Winnow · Reed","home-page.rework.technical.stack.visual.layer.4":"NUMERICS    Numerus · FMI","home-page.rework.technical.stack.visual.caption":"Change one layer without pretending the others do not exist","home-page.rework.technical.proof.eyebrow":"The engineering standard","home-page.rework.technical.proof.title.0":"If it matters, leave a trail","home-page.rework.technical.proof.title.1":"if it changes, replay it","home-page.rework.technical.proof.body":"Dweve treats observability as part of the result. A useful system gives you the path, the constraints, and the artefact needed to inspect a decision without reconstructing the story from scattered logs.","home-page.rework.technical.proof.pill.0":"Trace events","home-page.rework.technical.proof.pill.1":"Stable artefacts","home-page.rework.technical.proof.pill.2":"Offline inspection","home-page.rework.technical.proof.side.label":"What survives","home-page.rework.technical.proof.side.pill":"EVIDENCE","home-page.rework.technical.proof.side.0.label":"The input","home-page.rework.technical.proof.side.0.value":"Bound to the run","home-page.rework.technical.proof.side.1.label":"The route","home-page.rework.technical.proof.side.1.value":"Named, not inferred","home-page.rework.technical.proof.side.2.label":"The output","home-page.rework.technical.proof.side.2.value":"Packaged with context","home-page.rework.technical.proof.side.3.label":"The replay","home-page.rework.technical.proof.side.3.value":"Runnable without theatre","home-page.rework.technical.proof.visual.header":"evidence bundle","home-page.rework.technical.proof.visual.status":"SEALED","home-page.rework.technical.proof.visual.live":"LIVE","home-page.rework.technical.proof.visual.item.0":"01  request.json          4.8 KB","home-page.rework.technical.proof.visual.item.1":"02  route.trace            12 events","home-page.rework.technical.proof.visual.item.2":"03  constraints.proof       6 checks","home-page.rework.technical.proof.visual.item.3":"04  result.receipt           1 answer","home-page.rework.technical.proof.visual.footer":"BLAKE3 ROOT  ·  OFFLINE CHECK AVAILABLE  ·  NO HIDDEN STEP","home-page.rework.consumer.workspace.eyebrow":"A workspace for real questions","home-page.rework.consumer.workspace.title.0":"Bring the context with you","home-page.rework.consumer.workspace.title.1":"so the answer can help","home-page.rework.consumer.workspace.body":"The useful part of an assistant is not the chat bubble. It is remembering the files, notes, decisions, and small routines around the question so you can finish something instead of starting over.","home-page.rework.consumer.workspace.pill.0":"Your files","home-page.rework.consumer.workspace.pill.1":"A remembered thread","home-page.rework.consumer.workspace.pill.2":"Sources when you need them","home-page.rework.consumer.workspace.side.label":"A normal afternoon","home-page.rework.consumer.workspace.side.pill":"FABRIC","home-page.rework.consumer.workspace.side.0.label":"Ask","home-page.rework.consumer.workspace.side.0.value":"Use your own words","home-page.rework.consumer.workspace.side.1.label":"Add","home-page.rework.consumer.workspace.side.1.value":"Bring the useful file","home-page.rework.consumer.workspace.side.2.label":"Check","home-page.rework.consumer.workspace.side.2.value":"Open the source","home-page.rework.consumer.workspace.side.3.label":"Keep","home-page.rework.consumer.workspace.side.3.value":"Save the finished answer","home-page.rework.consumer.workspace.visual.thread":"Plan a weekend in Rotterdam","home-page.rework.consumer.workspace.visual.question":"Can you turn my saved places into a simple Saturday route, with the museum first and a quiet lunch nearby?","home-page.rework.consumer.workspace.visual.answer":"Start at the museum at 10:00, then walk to the harbour. I used your saved places and the opening hours in Rotterdam-notes.pdf.","home-page.rework.consumer.workspace.visual.source.0":"Rotterdam-notes.pdf","home-page.rework.consumer.workspace.visual.source.1":"saved-places.txt","home-page.rework.consumer.workspace.visual.workspace.badge":"MANAGED MESH","home-page.rework.consumer.workspace.visual.workspace.folder.0":"Weekend plans","home-page.rework.consumer.workspace.visual.workspace.folder.1":"Saved places","home-page.rework.consumer.workspace.visual.workspace.folder.2":"Notes","home-page.rework.consumer.workspace.visual.workspace.pinned.0":"Rotterdam route","home-page.rework.consumer.workspace.visual.workspace.pinned.1":"Museum shortlist","home-page.rework.consumer.workspace.visual.workspace.meta":"Answered with 2 sources","home-page.rework.consumer.workspace.visual.workspace.placeholder":"Ask about your files or plans","home-page.rework.consumer.workspace.visual.workspace.suggestion.0":"Make it shorter","home-page.rework.consumer.workspace.visual.workspace.suggestion.1":"Save this route","home-page.rework.consumer.workspace.visual.footer":"SAVED TO WEEKEND PLANS  ·  2 SOURCES  ·  READY TO SHARE","home-page.rework.consumer.flow.eyebrow":"How it works in practice","home-page.rework.consumer.flow.title.0":"Less repeating yourself","home-page.rework.consumer.flow.title.1":"more getting things done","home-page.rework.consumer.flow.body":"Fabric keeps the thread, not a performance of certainty. You can see what it used, correct it when needed, and turn a good answer into a small workflow you can use again.","home-page.rework.consumer.flow.pill.0":"Remembered context","home-page.rework.consumer.flow.pill.1":"Plain explanations","home-page.rework.consumer.flow.pill.2":"Reusable routines","home-page.rework.consumer.flow.side.label":"The small loop","home-page.rework.consumer.flow.side.pill":"NO RESET","home-page.rework.consumer.flow.side.0.label":"You ask","home-page.rework.consumer.flow.side.0.value":"Start wherever you are","home-page.rework.consumer.flow.side.1.label":"Fabric remembers","home-page.rework.consumer.flow.side.1.value":"The useful context","home-page.rework.consumer.flow.side.2.label":"You check","home-page.rework.consumer.flow.side.2.value":"The source behind it","home-page.rework.consumer.flow.side.3.label":"You keep","home-page.rework.consumer.flow.side.3.value":"The result or routine","home-page.rework.consumer.flow.visual.header":"from question to routine","home-page.rework.consumer.flow.visual.status":"READY TO REUSE","home-page.rework.consumer.flow.visual.0":"01  Ask in the words you use","home-page.rework.consumer.flow.visual.1":"02  Add context once, not five times","home-page.rework.consumer.flow.visual.2":"03  Check the useful source","home-page.rework.consumer.flow.visual.3":"04  Save the pattern for next time","home-page.rework.consumer.flow.visual.footer":"YOUR THREAD  ·  YOUR SOURCES  ·  YOUR NEXT STEP","home-page.rework.consumer.control.eyebrow":"Private by default","home-page.rework.consumer.control.title.0":"Keep the useful parts","home-page.rework.consumer.control.title.1":"and decide what leaves","home-page.rework.consumer.control.body":"Your workspace should feel like a place you can return to, not a box you have to feed. Keep your files and notes together, see the sources behind an answer, and choose the boundary that fits your life.","home-page.rework.consumer.control.pill.0":"managed Mesh","home-page.rework.consumer.control.pill.1":"No training on your content","home-page.rework.consumer.control.pill.2":"Exportable work","home-page.rework.consumer.control.side.label":"Your controls","home-page.rework.consumer.control.side.pill":"YOURS","home-page.rework.consumer.control.side.0.label":"Where it lives","home-page.rework.consumer.control.side.0.value":"European infrastructure","home-page.rework.consumer.control.side.1.label":"What it sees","home-page.rework.consumer.control.side.1.value":"Only what you add","home-page.rework.consumer.control.side.2.label":"What it learns","home-page.rework.consumer.control.side.2.value":"Not from your content","home-page.rework.consumer.control.side.3.label":"What you keep","home-page.rework.consumer.control.side.3.value":"The work and the record","home-page.rework.consumer.control.visual.header":"workspace settings","home-page.rework.consumer.control.visual.status":"YOUR CHOICE","home-page.rework.consumer.control.visual.item.0":"EU region                         active","home-page.rework.consumer.control.visual.item.1":"Use saved context                  on","home-page.rework.consumer.control.visual.item.2":"Sources on every answer           on","home-page.rework.consumer.control.visual.item.3":"Use content to train models       off","home-page.rework.consumer.control.visual.caption":"The defaults are clear, and the important choices stay close to the work","home-page.rework.consumer.sources.eyebrow":"Answers you can open","home-page.rework.consumer.sources.title.0":"See what shaped the answer","home-page.rework.consumer.sources.title.1":"without reading everything again","home-page.rework.consumer.sources.body":"Fabric shows the useful trail behind an answer: which file supplied a date, where a preference came from, and what still needs checking. The answer stays readable while the evidence remains one tap away.","home-page.rework.consumer.sources.pill.0":"Visible sources","home-page.rework.consumer.sources.pill.1":"Useful passages","home-page.rework.consumer.sources.pill.2":"Open in place","home-page.rework.consumer.sources.side.label":"Behind one answer","home-page.rework.consumer.sources.side.pill":"3 SOURCES","home-page.rework.consumer.sources.side.0.label":"Date","home-page.rework.consumer.sources.side.0.value":"From the booking email","home-page.rework.consumer.sources.side.1.label":"Place","home-page.rework.consumer.sources.side.1.value":"From your saved list","home-page.rework.consumer.sources.side.2.label":"Preference","home-page.rework.consumer.sources.side.2.value":"From your note","home-page.rework.consumer.sources.side.3.label":"Unclear","home-page.rework.consumer.sources.side.3.value":"Marked for you","home-page.rework.consumer.sources.visual.header":"answer and source trail","home-page.rework.consumer.sources.visual.status":"OPENABLE","home-page.rework.consumer.sources.visual.answer.label":"SUGGESTED PLAN","home-page.rework.consumer.sources.visual.answer.body":"The museum opens at 10:00. Leave forty minutes for the harbour walk and keep lunch near the quiet courtyard you saved.","home-page.rework.consumer.sources.visual.source.0.name":"museum-booking.eml","home-page.rework.consumer.sources.visual.source.0.used":"Opening time and ticket window","home-page.rework.consumer.sources.visual.source.0.status":"USED","home-page.rework.consumer.sources.visual.source.1.name":"saved-places.txt","home-page.rework.consumer.sources.visual.source.1.used":"Harbour route and courtyard","home-page.rework.consumer.sources.visual.source.1.status":"USED","home-page.rework.consumer.sources.visual.source.2.name":"weekend-notes.pdf","home-page.rework.consumer.sources.visual.source.2.used":"Quiet lunch preference","home-page.rework.consumer.sources.visual.source.2.status":"USED","home-page.rework.consumer.sources.visual.caption":"Open any source without losing your place in the answer","home-page.rework.consumer.sources.visual.footer":"ANSWER FIRST  ·  SOURCES ATTACHED  ·  NOTHING HIDDEN","home-page.rework.consumer.correct.eyebrow":"Your correction carries forward","home-page.rework.consumer.correct.title.0":"Change it once","home-page.rework.consumer.correct.title.1":"keep the better version","home-page.rework.consumer.correct.body":"A helpful workspace should improve when you correct it. Change the time, remove an assumption, or add a preference and Fabric keeps the revised result with the reason, rather than quietly pretending the first answer never happened.","home-page.rework.consumer.correct.pill.0":"Edit in place","home-page.rework.consumer.correct.pill.1":"Reason kept","home-page.rework.consumer.correct.pill.2":"Earlier version available","home-page.rework.consumer.correct.side.label":"One small correction","home-page.rework.consumer.correct.side.pill":"SAVED","home-page.rework.consumer.correct.side.0.label":"Original","home-page.rework.consumer.correct.side.0.value":"Lunch at 12:00","home-page.rework.consumer.correct.side.1.label":"Your change","home-page.rework.consumer.correct.side.1.value":"Make it 13:00","home-page.rework.consumer.correct.side.2.label":"Reason","home-page.rework.consumer.correct.side.2.value":"More time at museum","home-page.rework.consumer.correct.side.3.label":"Next plan","home-page.rework.consumer.correct.side.3.value":"Uses the new choice","home-page.rework.consumer.correct.visual.header":"revision record","home-page.rework.consumer.correct.visual.status":"YOU CHANGED IT","home-page.rework.consumer.correct.visual.before.label":"BEFORE","home-page.rework.consumer.correct.visual.before.body":"Lunch at 12:00 beside the harbour.","home-page.rework.consumer.correct.visual.before.state":"Earlier version kept","home-page.rework.consumer.correct.visual.after.label":"AFTER","home-page.rework.consumer.correct.visual.after.body":"Lunch at 13:00 after a longer museum visit.","home-page.rework.consumer.correct.visual.after.state":"Current version","home-page.rework.consumer.correct.visual.record":"Reason: more time at the museum","home-page.rework.consumer.correct.visual.saved":"Saved to the thread","home-page.rework.consumer.correct.visual.footer":"YOUR EDIT  ·  YOUR REASON  ·  THE EARLIER VERSION REMAINS","home-page.rework.consumer.routines.eyebrow":"Useful work can repeat","home-page.rework.consumer.routines.title.0":"Turn a good result","home-page.rework.consumer.routines.title.1":"into a quiet routine","home-page.rework.consumer.routines.body":"When a task comes back every week, save the useful pattern instead of rebuilding it. Fabric can gather the same kind of material, prepare the same first pass, and leave the final choice with you.","home-page.rework.consumer.routines.pill.0":"Use again","home-page.rework.consumer.routines.pill.1":"Review before sending","home-page.rework.consumer.routines.pill.2":"Pause whenever you want","home-page.rework.consumer.routines.side.label":"The weekly rhythm","home-page.rework.consumer.routines.side.pill":"YOURS","home-page.rework.consumer.routines.side.0.label":"Collect","home-page.rework.consumer.routines.side.0.value":"Bring new notes together","home-page.rework.consumer.routines.side.1.label":"Prepare","home-page.rework.consumer.routines.side.1.value":"Make the first draft","home-page.rework.consumer.routines.side.2.label":"Review","home-page.rework.consumer.routines.side.2.value":"You make the call","home-page.rework.consumer.routines.side.3.label":"Keep","home-page.rework.consumer.routines.side.3.value":"Save the finished result","home-page.rework.consumer.routines.visual.header":"a routine you can inspect","home-page.rework.consumer.routines.visual.status":"NEXT RUN FRIDAY","home-page.rework.consumer.routines.visual.moment.0.when":"MONDAY","home-page.rework.consumer.routines.visual.moment.0.title":"New notes arrive","home-page.rework.consumer.routines.visual.moment.0.body":"Kept in the same folder","home-page.rework.consumer.routines.visual.moment.1.when":"THURSDAY","home-page.rework.consumer.routines.visual.moment.1.title":"First pass prepared","home-page.rework.consumer.routines.visual.moment.1.body":"Sources stay attached","home-page.rework.consumer.routines.visual.moment.2.when":"FRIDAY","home-page.rework.consumer.routines.visual.moment.2.title":"You review it","home-page.rework.consumer.routines.visual.moment.2.body":"Nothing sends itself","home-page.rework.consumer.routines.visual.moment.3.when":"AFTER","home-page.rework.consumer.routines.visual.moment.3.title":"Result stays useful","home-page.rework.consumer.routines.visual.moment.3.body":"Ready for the next week","home-page.rework.consumer.routines.visual.saved":"Routine saved with a review step before anything leaves your workspace","home-page.rework.consumer.routines.visual.footer":"REPEAT THE PATTERN  ·  KEEP THE DECISION  ·  PAUSE ANY TIME","home-page.rework.consumer.sharing.eyebrow":"Share the result, not the room","home-page.rework.consumer.sharing.title.0":"Invite people deliberately","home-page.rework.consumer.sharing.title.1":"keep the rest private","home-page.rework.consumer.sharing.body":"A finished plan may need another pair of eyes, but that does not mean opening your whole workspace. Share one result, choose what each person may do, and keep your notes and unrelated files out of view.","home-page.rework.consumer.sharing.pill.0":"One item at a time","home-page.rework.consumer.sharing.pill.1":"Clear access","home-page.rework.consumer.sharing.pill.2":"Private notes stay private","home-page.rework.consumer.sharing.side.label":"Who can do what","home-page.rework.consumer.sharing.side.pill":"3 PEOPLE","home-page.rework.consumer.sharing.side.0.label":"You","home-page.rework.consumer.sharing.side.0.value":"Own and edit","home-page.rework.consumer.sharing.side.1.label":"Sam","home-page.rework.consumer.sharing.side.1.value":"Can comment","home-page.rework.consumer.sharing.side.2.label":"Mila","home-page.rework.consumer.sharing.side.2.value":"Can view","home-page.rework.consumer.sharing.side.3.label":"Everyone else","home-page.rework.consumer.sharing.side.3.value":"No access","home-page.rework.consumer.sharing.visual.header":"share settings","home-page.rework.consumer.sharing.visual.status":"ONE ITEM","home-page.rework.consumer.sharing.visual.item":"Weekend plan","home-page.rework.consumer.sharing.visual.question":"Who should see this result?","home-page.rework.consumer.sharing.visual.person.0.initial":"YOU","home-page.rework.consumer.sharing.visual.person.0.name":"You","home-page.rework.consumer.sharing.visual.person.0.access":"Owner · can edit","home-page.rework.consumer.sharing.visual.person.1.initial":"SA","home-page.rework.consumer.sharing.visual.person.1.name":"Sam","home-page.rework.consumer.sharing.visual.person.1.access":"Can comment","home-page.rework.consumer.sharing.visual.person.2.initial":"MI","home-page.rework.consumer.sharing.visual.person.2.name":"Mila","home-page.rework.consumer.sharing.visual.person.2.access":"Can view","home-page.rework.consumer.sharing.visual.private":"Other folders remain private","home-page.rework.consumer.sharing.visual.owner":"You can revoke access","home-page.rework.consumer.sharing.visual.footer":"SHARE ONE RESULT  ·  KEEP THE WORKSPACE  ·  CHANGE ACCESS ANY TIME","home-page.rework.consumer.behind.eyebrow":"One workspace on the surface","home-page.rework.consumer.behind.title.0":"Use Fabric","home-page.rework.consumer.behind.title.1":"let the system stay underneath","home-page.rework.consumer.behind.body":"You should not have to choose engines, connect services, or learn a product map before asking a question. Fabric is the place you use. The rest of Dweve works underneath to read, organise, check, and remember the work.","home-page.rework.consumer.behind.pill.0":"One front door","home-page.rework.consumer.behind.pill.1":"No system setup","home-page.rework.consumer.behind.pill.2":"Complexity stays underneath","home-page.rework.consumer.behind.side.label":"What you notice","home-page.rework.consumer.behind.side.pill":"FABRIC","home-page.rework.consumer.behind.side.0.label":"Your folders","home-page.rework.consumer.behind.side.0.value":"Kept together","home-page.rework.consumer.behind.side.1.label":"Your questions","home-page.rework.consumer.behind.side.1.value":"Asked normally","home-page.rework.consumer.behind.side.2.label":"Your sources","home-page.rework.consumer.behind.side.2.value":"Shown clearly","home-page.rework.consumer.behind.side.3.label":"Your routines","home-page.rework.consumer.behind.side.3.value":"Ready to repeat","home-page.rework.consumer.behind.visual.header":"behind your workspace","home-page.rework.consumer.behind.visual.status":"ONE SURFACE","home-page.rework.consumer.behind.visual.surface":"The only place you need to open","home-page.rework.consumer.behind.visual.row.0.title":"Read the material","home-page.rework.consumer.behind.visual.row.0.body":"Different files, one workspace","home-page.rework.consumer.behind.visual.row.1.title":"Find the useful context","home-page.rework.consumer.behind.visual.row.1.body":"The right passage stays attached","home-page.rework.consumer.behind.visual.row.2.title":"Check the answer","home-page.rework.consumer.behind.visual.row.2.body":"Sources and changes remain visible","home-page.rework.consumer.behind.visual.row.3.title":"Keep the routine","home-page.rework.consumer.behind.visual.row.3.body":"Good work is ready to reuse","home-page.rework.consumer.behind.visual.caption":"The system does the joining; Fabric keeps the experience simple","home-page.rework.consumer.behind.visual.footer":"ONE WORKSPACE  ·  THE SYSTEM UNDERNEATH  ·  NO PRODUCT MAP TO LEARN","home-page.rework.consumer.exit.eyebrow":"Leaving should be ordinary","home-page.rework.consumer.exit.title.0":"Take the work with you","home-page.rework.consumer.exit.title.1":"without asking permission","home-page.rework.consumer.exit.body":"Your files, answers, sources, and saved routines should not become trapped inside a helpful tool. Export the useful record, move it somewhere else, or delete the workspace when it has done its job.","home-page.rework.consumer.exit.pill.0":"Export the record","home-page.rework.consumer.exit.pill.1":"Readable files","home-page.rework.consumer.exit.pill.2":"Delete when finished","home-page.rework.consumer.exit.side.label":"What comes with you","home-page.rework.consumer.exit.side.pill":"READY","home-page.rework.consumer.exit.side.0.label":"Files","home-page.rework.consumer.exit.side.0.value":"Originals included","home-page.rework.consumer.exit.side.1.label":"Answers","home-page.rework.consumer.exit.side.1.value":"Readable outside Fabric","home-page.rework.consumer.exit.side.2.label":"Sources","home-page.rework.consumer.exit.side.2.value":"Links and passages","home-page.rework.consumer.exit.side.3.label":"Routines","home-page.rework.consumer.exit.side.3.value":"Steps in plain form","home-page.rework.consumer.exit.visual.header":"workspace export","home-page.rework.consumer.exit.visual.status":"READY TO MOVE","home-page.rework.consumer.exit.visual.bundle":"weekend-plans-export","home-page.rework.consumer.exit.visual.bundle.note":"The work, sources, and change record","home-page.rework.consumer.exit.visual.ready":"COMPLETE","home-page.rework.consumer.exit.visual.file.0":"plans.md","home-page.rework.consumer.exit.visual.file.1":"sources.json","home-page.rework.consumer.exit.visual.file.2":"originals/","home-page.rework.consumer.exit.visual.file.3":"changes.txt","home-page.rework.consumer.exit.visual.keep":"KEEP HERE","home-page.rework.consumer.exit.visual.move":"MOVE ELSEWHERE","home-page.rework.consumer.exit.visual.delete":"DELETE WORKSPACE","home-page.rework.consumer.exit.visual.footer":"YOUR WORK  ·  READABLE OUTSIDE FABRIC  ·  NO LOCKED DOOR","home-page.home.audit.titleLead":"A decision is only useful","home-page.home.audit.titleAccent":"when its record survives","home-page.home.audit.body":"The review packet forms while the work moves. Source, rule, owner, and replay stay attached to the decision, so a later audit starts with evidence instead of reconstruction.","home-page.home.audit.question":"Can this decision still be defended after the people and systems around it have changed?","home-page.home.audit.answer":"Yes. The result carries the source used, the rule applied, the named reviewer, and a replayable record of the path taken.","home-page.home.audit.status":"RECORD COMPLETE","home-page.home.audit.step0":"Original passage and version captured","home-page.home.audit.step1":"Applied rule named beside the result","home-page.home.audit.step2":"Reviewer and final action recorded","home-page.home.audit.step3":"Same path can be checked again","home-page.home.substrate.titleLead":"Determinism is a stack property","home-page.home.substrate.titleAccent":"not a label on the output","home-page.home.substrate.body":"Arithmetic, hashing, representation, and reasoning each keep an explicit contract. The result is reproducible because every layer preserves the same invariants, not because a final API says it is.","home-page.home.substrate.status":"INVARIANTS HOLD","home-page.home.constraint.titleLead":"Constraints expose the path","home-page.home.constraint.titleAccent":"weights conceal","home-page.home.constraint.body":"A discrete decision can name the facts it accepted, the rule that fired, and the branch it rejected. Inspect the mechanism first; only then judge the product claim built on top.","home-page.home.constraint.question":"Why did this input reach this state?","home-page.home.constraint.answer":"Three premises satisfied the policy rule; one conflicting branch was rejected; the accepted path is attached to the result.","home-page.home.constraint.status":"PATH PROVEN","home-page.home.constraint.step0":"Normalised facts enter as explicit values","home-page.home.constraint.step1":"The policy boundary is evaluated directly","home-page.home.constraint.step2":"Conflicting branches are recorded, not hidden","home-page.home.constraint.step3":"The accepted route leaves a portable receipt","home-page.home.constraint.accepted":"The premises satisfy the named policy rule","home-page.home.constraint.rejected":"The conflicting branch fails the boundary check","home-page.home.benchmark.titleLead":"Read the result as a profile","home-page.home.benchmark.titleAccent":"not a trophy number","home-page.home.benchmark.body":"A single speedup hides where the work went and what trade-off was made. This run profile keeps workload, unit, hardware, and guard test beside each figure, so the shape stays visible and comparable.","home-page.home.benchmark.status":"RUN VERIFIED","home-page.home.visual.request":"REQUEST","home-page.home.visual.reviewedAnswer":"REVIEWED ANSWER","home-page.home.visual.bitIdentical":"BIT IDENTICAL","home-page.home.visual.pass":"PASS","home-page.home.visual.logic":"IF / AND / NOT","home-page.home.visual.premises":"PREMISES","home-page.home.visual.accepted":"ACCEPTED","home-page.home.visual.rejected":"REJECTED","home-page.home.visual.sealed":"SEALED","home-page.next.business.operating.eyebrow":"Turn queues into flow","home-page.next.business.operating.title.0":"Move each request","home-page.next.business.operating.title.1":"through one clear path","home-page.next.business.operating.body":"Fabric keeps intake, sources, checks, exceptions, ownership, and approval in one workflow. Teams see queue position, blockers, and the next responsible person. Each completed decision leaves a path that can be reused and measured.","home-page.next.business.operating.pill.0":"Visible queue","home-page.next.business.operating.pill.1":"Named gates","home-page.next.business.operating.pill.2":"Reusable path","home-page.next.business.operating.footer":"Each decision improves the next run","home-page.next.business.operating.side.title":"Workflow state","home-page.next.business.operating.side.tag":"FLOW VISIBLE","home-page.next.business.operating.side.0.label":"Intake","home-page.next.business.operating.side.0.value":"Question, files, and due date","home-page.next.business.operating.side.1.label":"Evidence","home-page.next.business.operating.side.1.value":"Policies, contracts, and records","home-page.next.business.operating.side.2.label":"Review","home-page.next.business.operating.side.2.value":"Exceptions and blockers visible","home-page.next.business.operating.side.3.label":"Approval","home-page.next.business.operating.side.3.value":"Owner closes the record","home-page.next.business.operating.side.foot":"One path from intake to approval","home-page.next.business.operating.detail.label":"What changes in practice","home-page.next.business.operating.detail.0":"The queue is not only a status list. Each gate names the evidence, exception, and person needed before work can move on. Work that is not ready stops at the gate that says what is still missing, rather than drifting between inboxes.","home-page.next.business.operating.detail.1":"Because the route is retained with the decision, teams can compare the next run with the last one instead of rebuilding the story from messages. The same path can then be reused, so a second request does not start from an empty page.","home-page.next.business.operating.visual.title":"Workflow state","home-page.next.business.operating.visual.status":"REVIEW READY","home-page.next.business.operating.visual.foot":"One path from intake to approval","home-page.next.business.operating.visual.stage.0.title":"Receive","home-page.next.business.operating.visual.stage.0.body":"Ask, files, due date","home-page.next.business.operating.visual.stage.0.owner":"Operations desk","home-page.next.business.operating.visual.stage.0.state":"Queued","home-page.next.business.operating.visual.stage.1.title":"Ground","home-page.next.business.operating.visual.stage.1.body":"Policy and records","home-page.next.business.operating.visual.stage.1.owner":"Fabric","home-page.next.business.operating.visual.stage.1.state":"Sources attached","home-page.next.business.operating.visual.stage.2.title":"Review","home-page.next.business.operating.visual.stage.2.body":"Exceptions and risk","home-page.next.business.operating.visual.stage.2.owner":"Subject owner","home-page.next.business.operating.visual.stage.2.state":"One exception","home-page.next.business.operating.visual.stage.3.title":"Assign","home-page.next.business.operating.visual.stage.3.body":"Accountable owner","home-page.next.business.operating.visual.stage.3.owner":"Procurement lead","home-page.next.business.operating.visual.stage.3.state":"Action named","home-page.next.business.operating.visual.stage.4.title":"Approve","home-page.next.business.operating.visual.stage.4.body":"Action recorded","home-page.next.business.operating.visual.stage.4.owner":"Budget holder","home-page.next.business.operating.visual.stage.4.state":"Decision ready","home-page.next.business.operating.visual.outcome.label":"Reusable path","home-page.next.business.operating.visual.outcome.value":"Decision workflow","home-page.next.business.operating.visual.outcome.note":"Route, owner, and approval retained","home-page.next.business.operating.visual.metric.0.label":"Queue age","home-page.next.business.operating.visual.metric.0.value":"Measured per stage","home-page.next.business.operating.visual.metric.1.label":"Rework","home-page.next.business.operating.visual.metric.1.value":"Compared with baseline","home-page.next.business.operating.visual.metric.2.label":"Exceptions","home-page.next.business.operating.visual.metric.2.value":"Visible before approval","home-page.next.business.record.eyebrow":"One record, one decision","home-page.next.business.record.title.0":"Keep the evidence","home-page.next.business.record.title.1":"beside the decision","home-page.next.business.record.body":"Fabric keeps the proposed decision beside its sources, open risk, owner, and approval state. Operations, finance, and governance inspect the same record instead of reconciling separate documents after the meeting.","home-page.next.business.record.pill.0":"Basis attached","home-page.next.business.record.pill.1":"Risk open","home-page.next.business.record.pill.2":"Owner named","home-page.next.business.record.footer":"Sources, risk, owner, and approval state stay in one decision record","home-page.next.business.record.side.title":"Decision record","home-page.next.business.record.side.tag":"ONE RECORD","home-page.next.business.record.side.0.label":"Basis","home-page.next.business.record.side.0.value":"Sources attached to proposal","home-page.next.business.record.side.1.label":"Owner","home-page.next.business.record.side.1.value":"Named accountable owner","home-page.next.business.record.side.2.label":"Open risk","home-page.next.business.record.side.2.value":"Unresolved risk stays visible","home-page.next.business.record.side.3.label":"Decision","home-page.next.business.record.side.3.value":"Return, change, or approve","home-page.next.business.record.side.foot":"Everyone reads the same record","home-page.next.business.record.detail.label":"Why it matters","home-page.next.business.record.detail.0":"A proposal is easier to challenge when its sources, open risk, owner, and approval state sit beside it rather than in separate files. Each of those is attached to the decision itself, so a reviewer opens one object instead of four.","home-page.next.business.record.detail.1":"The record keeps judgement visible without presenting it as source truth, so governance can see what is known and what still needs a call. An open risk stays open in the record until the named owner closes it.","home-page.next.business.record.visual.title":"Decision record","home-page.next.business.record.visual.status":"REVIEW OPEN","home-page.next.business.record.visual.foot":"Everyone reads the same record","home-page.next.business.record.visual.question.label":"Supplier review","home-page.next.business.record.visual.question.value":"Can this supplier meet the new data boundary?","home-page.next.business.record.visual.question.note":"Retention covered, incident owner missing","home-page.next.business.record.visual.flag.0":"Basis attached","home-page.next.business.record.visual.flag.1":"Risk open","home-page.next.business.record.visual.flag.2":"Owner named","home-page.next.business.record.visual.field.0.label":"Sources","home-page.next.business.record.visual.field.0.value":"Contract, risk register","home-page.next.business.record.visual.field.1.label":"Owner","home-page.next.business.record.visual.field.1.value":"Procurement lead","home-page.next.business.record.visual.field.2.label":"Risk","home-page.next.business.record.visual.field.2.value":"Incident owner missing","home-page.next.business.record.visual.field.3.label":"Approval","home-page.next.business.record.visual.field.3.value":"Reviewer pending","home-page.next.business.record.visual.field.4.label":"Next action","home-page.next.business.record.visual.field.4.value":"Name incident owner","home-page.next.business.record.visual.signoff.owner":"Procurement lead","home-page.next.business.record.visual.signoff.state":"Review open","home-page.next.business.record.visual.signoff.next":"Return to owner","home-page.next.business.whole-stack.eyebrow":"One operating chain","home-page.next.business.whole-stack.title.0":"One request can cross the stack","home-page.next.business.whole-stack.title.1":"without becoming eight projects","home-page.next.business.whole-stack.body":"Fabric is the operating surface. Nexus coordinates multi-agent work, Loom composes cognition, Spindle governs versioned knowledge, Aura changes software, Core provides the machine-learning framework, Mesh places eligible work, and Charter keeps rights and responsibilities explicit. Shared contracts let one record cross only the product boundaries the work actually needs.","home-page.next.business.whole-stack.pill.0":"Eight products","home-page.next.business.whole-stack.pill.1":"Shared contracts","home-page.next.business.whole-stack.pill.2":"Fewer handovers","home-page.next.business.whole-stack.footer":"Eight capabilities, one accountable path","home-page.next.business.whole-stack.side.title":"Dweve capabilities","home-page.next.business.whole-stack.side.tag":"EIGHT PRODUCTS","home-page.next.business.whole-stack.side.0.label":"Work surface","home-page.next.business.whole-stack.side.0.value":"Fabric keeps work and decisions together","home-page.next.business.whole-stack.side.1.label":"Knowledge and cognition","home-page.next.business.whole-stack.side.1.value":"Loom and Spindle ground the work","home-page.next.business.whole-stack.side.2.label":"Agents and delivery","home-page.next.business.whole-stack.side.2.value":"Nexus coordinates; Aura changes software","home-page.next.business.whole-stack.side.3.label":"Execution and accountability","home-page.next.business.whole-stack.side.3.value":"Core executes, Mesh places, Charter governs","home-page.next.business.whole-stack.side.foot":"One accountable operating path","home-page.next.business.whole-stack.visual.title":"Dweve capabilities","home-page.next.business.whole-stack.visual.status":"CHAIN CONNECTED","home-page.next.business.whole-stack.visual.foot":"One accountable operating path","home-page.next.business.whole-stack.visual.group.0.title":"Work and operations","home-page.next.business.whole-stack.visual.group.0.item.0.name":"Fabric","home-page.next.business.whole-stack.visual.group.0.item.0.body":"Work and decisions","home-page.next.business.whole-stack.visual.group.0.item.1.name":"Nexus","home-page.next.business.whole-stack.visual.group.0.item.1.body":"Agent operations","home-page.next.business.whole-stack.visual.group.1.title":"Cognition and knowledge","home-page.next.business.whole-stack.visual.group.1.item.0.name":"Loom","home-page.next.business.whole-stack.visual.group.1.item.0.body":"Cognitive graphs","home-page.next.business.whole-stack.visual.group.1.item.1.name":"Spindle","home-page.next.business.whole-stack.visual.group.1.item.1.body":"Versioned knowledge","home-page.next.business.whole-stack.visual.group.2.title":"Development and execution","home-page.next.business.whole-stack.visual.group.2.item.0.name":"Aura","home-page.next.business.whole-stack.visual.group.2.item.0.body":"Development agents","home-page.next.business.whole-stack.visual.group.2.item.1.name":"Core","home-page.next.business.whole-stack.visual.group.2.item.1.body":"Execution runtime","home-page.next.business.whole-stack.visual.group.3.title":"Placement and accountability","home-page.next.business.whole-stack.visual.group.3.item.0.name":"Mesh","home-page.next.business.whole-stack.visual.group.3.item.0.body":"Policy-aware work placement","home-page.next.business.whole-stack.visual.group.3.item.1.name":"Charter","home-page.next.business.whole-stack.visual.group.3.item.1.body":"Explicit rights and responsibilities","home-page.next.business.whole-stack.visual.extension.label":"Separate target portfolio","home-page.next.business.whole-stack.visual.extension.title":"Kera","home-page.next.business.whole-stack.visual.extension.body":"Compiles the accepted graph for the agreed target families when the operation needs it","home-page.next.business.whole-stack.visual.extension.state":"Scoped separately","home-page.next.business.whole-stack.visual.thread":"One record crosses the stack","home-page.next.business.portfolio.eyebrow":"A scope people can understand","home-page.next.business.portfolio.title.0":"Buy the operating outcome","home-page.next.business.portfolio.title.1":"not a pile of disconnected tools","home-page.next.business.portfolio.body":"Start with the workflow, the people who own it, and the result that must improve. The Business Workspace supplies the operating surface and the platform behind it. Customer-controlled deployment, Kera target portfolios, onboarding, and support are scoped only when the workflow requires them, so commercial boundaries stay as clear as operational ones.","home-page.next.business.portfolio.pill.0":"Outcome first","home-page.next.business.portfolio.pill.1":"Boundaries named","home-page.next.business.portfolio.pill.2":"Nothing implied","home-page.next.business.portfolio.footer":"The scope names the workflow, accountable owner, boundary, and expansion","home-page.next.business.portfolio.side.title":"Scope logic","home-page.next.business.portfolio.side.tag":"OUTCOME FIRST","home-page.next.business.portfolio.side.0.label":"Workflow","home-page.next.business.portfolio.side.0.value":"Name the work and the accountable owner","home-page.next.business.portfolio.side.1.label":"Baseline","home-page.next.business.portfolio.side.1.value":"Agree what improvement means","home-page.next.business.portfolio.side.2.label":"Boundary","home-page.next.business.portfolio.side.2.value":"Choose control, placement, and support","home-page.next.business.portfolio.side.3.label":"Expansion","home-page.next.business.portfolio.side.3.value":"Add scope after the proof","home-page.next.business.portfolio.side.foot":"Scope follows the operating case","home-page.next.business.portfolio.detail.label":"The commercial boundary","home-page.next.business.portfolio.detail.0":"Start with the workflow and the owner, then name the deployment, support, and target scope that the first proof actually requires. Anything beyond that first proof stays a later decision with a justification of its own.","home-page.next.business.portfolio.detail.1":"This keeps a platform responsibility distinct from a separately agreed Kera target or operating perimeter. Nothing is implied by the catalogue alone, so what is in scope is what has been written down and agreed.","home-page.next.business.portfolio.visual.title":"Commercial scope","home-page.next.business.portfolio.visual.status":"BOUNDARIES EXPLICIT","home-page.next.business.portfolio.visual.foot":"Every addition answers an operating need","home-page.next.business.portfolio.visual.domain.0.title":"Business Workspace","home-page.next.business.portfolio.visual.domain.0.product.0.name":"Fabric Web","home-page.next.business.portfolio.visual.domain.0.product.0.job":"The surface teams use for work and decisions","home-page.next.business.portfolio.visual.domain.0.product.0.gain":"Included user path","home-page.next.business.portfolio.visual.domain.0.product.1.name":"Dweve platform","home-page.next.business.portfolio.visual.domain.0.product.1.job":"Cognition, knowledge, agents, execution, and placement behind the workflow","home-page.next.business.portfolio.visual.domain.0.product.1.gain":"One managed service","home-page.next.business.portfolio.visual.domain.1.title":"Controlled deployment","home-page.next.business.portfolio.visual.domain.1.product.0.name":"Licensed operation","home-page.next.business.portfolio.visual.domain.1.product.0.job":"Run within the agreed customer-controlled perimeter","home-page.next.business.portfolio.visual.domain.1.product.0.gain":"Scoped by estate","home-page.next.business.portfolio.visual.domain.1.product.1.name":"Deployment boundary","home-page.next.business.portfolio.visual.domain.1.product.1.job":"Region, network path, responsibility, and service level","home-page.next.business.portfolio.visual.domain.1.product.1.gain":"Named in the order","home-page.next.business.portfolio.visual.domain.2.title":"Target software","home-page.next.business.portfolio.visual.domain.2.product.0.name":"Kera portfolio","home-page.next.business.portfolio.visual.domain.2.product.0.job":"Accepted target families and compiler output","home-page.next.business.portfolio.visual.domain.2.product.0.gain":"Contracted separately","home-page.next.business.portfolio.visual.domain.2.product.1.name":"Acceptance basis","home-page.next.business.portfolio.visual.domain.2.product.1.job":"Targets, outputs, support, and change boundary","home-page.next.business.portfolio.visual.domain.2.product.1.gain":"No implied coverage","home-page.next.business.portfolio.visual.domain.3.title":"Proof and support","home-page.next.business.portfolio.visual.domain.3.product.0.name":"First workflow","home-page.next.business.portfolio.visual.domain.3.product.0.job":"Baseline, integration, owners, and acceptance measure","home-page.next.business.portfolio.visual.domain.3.product.0.gain":"Proof before scale","home-page.next.business.portfolio.visual.domain.3.product.1.name":"Support scope","home-page.next.business.portfolio.visual.domain.3.product.1.job":"Coverage, response, responsibilities, and evidence","home-page.next.business.portfolio.visual.domain.3.product.1.gain":"Agreed, not assumed","home-page.next.business.cost.eyebrow":"Make capacity earn its place","home-page.next.business.cost.title.0":"Use what you have","home-page.next.business.cost.title.1":"before you add capacity","home-page.next.business.cost.body":"Mesh discovers eligible capacity across workstations, servers, and accelerators. Core runs supported machine-learning workloads; Kera compiles accepted graphs only for separately agreed target families. Operations can use the existing estate first, while finance sees demand and service needs before approving managed Mesh or dedicated licensed capacity.","home-page.next.business.cost.pill.0":"Existing estate","home-page.next.business.cost.pill.1":"Measured demand","home-page.next.business.cost.pill.2":"Deliberate scale","home-page.next.business.cost.footer":"Demand makes the case for spend","home-page.next.business.cost.side.title":"Capacity plan","home-page.next.business.cost.side.tag":"ESTATE VISIBLE","home-page.next.business.cost.side.0.label":"Estate","home-page.next.business.cost.side.0.value":"Eligible hardware already available","home-page.next.business.cost.side.1.label":"Demand","home-page.next.business.cost.side.1.value":"Workloads, deadlines, service needs","home-page.next.business.cost.side.2.label":"Placement","home-page.next.business.cost.side.2.value":"Each job matched to a target","home-page.next.business.cost.side.3.label":"Scale","home-page.next.business.cost.side.3.value":"Capacity added from observed need","home-page.next.business.cost.side.foot":"Demand justifies added spend","home-page.next.business.cost.detail.label":"The spend decision","home-page.next.business.cost.detail.0":"Mesh starts with capacity the organisation already owns, then shows the workload, deadline, and service requirement that make another route worth considering. Existing capacity is measured before anything new is proposed.","home-page.next.business.cost.detail.1":"It makes the decision legible: observed demand first, then a deliberate choice between managed and dedicated capacity. The reason for each addition stays attached to the decision that made it, so a later reader can see what changed.","home-page.next.business.cost.visual.title":"Capacity plan","home-page.next.business.cost.visual.status":"ESTATE CHECKED","home-page.next.business.cost.visual.foot":"Demand justifies added spend","home-page.next.business.cost.visual.request.label":"Workload","home-page.next.business.cost.visual.request.value":"Complete policy review by Friday","home-page.next.business.cost.visual.route.0.title":"Existing estate","home-page.next.business.cost.visual.route.0.body":"Match eligible hardware","home-page.next.business.cost.visual.route.0.when":"Use first","home-page.next.business.cost.visual.route.1.title":"Managed Mesh capacity","home-page.next.business.cost.visual.route.1.body":"Add managed capacity","home-page.next.business.cost.visual.route.1.when":"For service needs","home-page.next.business.cost.visual.route.2.title":"Dedicated capacity","home-page.next.business.cost.visual.route.2.body":"Reserve infrastructure","home-page.next.business.cost.visual.route.2.when":"For sustained demand","home-page.next.business.cost.visual.rule.label":"Spend rule","home-page.next.business.cost.visual.rule.value":"Observe before adding capacity","home-page.next.business.capacity.eyebrow":"Place work by operating need","home-page.next.business.capacity.title.0":"Route every workload","home-page.next.business.capacity.title.1":"to the right capacity","home-page.next.business.capacity.body":"Mesh filters available, local, managed Mesh, and isolated capacity by policy and risk, then weighs cost and urgency among eligible routes. Operations gets a visible placement decision; finance can use suitable existing capacity first and reserve higher-control routes for work that requires them.","home-page.next.business.capacity.pill.0":"Four lanes","home-page.next.business.capacity.pill.1":"Policy before price","home-page.next.business.capacity.pill.2":"Reason recorded","home-page.next.business.capacity.footer":"Every placement shows why that capacity fit the work","home-page.next.business.capacity.side.title":"Placement decision","home-page.next.business.capacity.side.tag":"ROUTE EXPLAINED","home-page.next.business.capacity.side.0.label":"Cost","home-page.next.business.capacity.side.0.value":"Prefer suitable capacity already paid for","home-page.next.business.capacity.side.1.label":"Urgency","home-page.next.business.capacity.side.1.value":"Match deadlines to available service","home-page.next.business.capacity.side.2.label":"Policy","home-page.next.business.capacity.side.2.value":"Keep data inside allowed routes","home-page.next.business.capacity.side.3.label":"Risk","home-page.next.business.capacity.side.3.value":"Raise isolation when exposure demands it","home-page.next.business.capacity.side.foot":"Eligible first, then cost and urgency","home-page.next.business.capacity.detail.label":"How placement is decided","home-page.next.business.capacity.detail.0":"Policy and fault boundaries remove routes that should not receive the work. Cost and urgency only rank the capacity that remains eligible, so eligibility is settled before price rather than the other way around.","home-page.next.business.capacity.detail.1":"The recorded reason gives operations a route to inspect and gives finance a basis for deciding when higher-control capacity is justified. Every placement carries the reason it was chosen, not only the result.","home-page.next.business.capacity.visual.title":"Capacity routing","home-page.next.business.capacity.visual.status":"PLACEMENT RESOLVED","home-page.next.business.capacity.visual.foot":"Four lanes, one recorded decision","home-page.next.business.capacity.visual.lane.0.title":"Available estate","home-page.next.business.capacity.visual.lane.0.body":"Eligible shared hardware","home-page.next.business.capacity.visual.lane.0.state":"Use when suitable","home-page.next.business.capacity.visual.lane.1.title":"Local capacity","home-page.next.business.capacity.visual.lane.1.body":"Device or site resources","home-page.next.business.capacity.visual.lane.1.state":"Owner priority","home-page.next.business.capacity.visual.lane.2.title":"managed Mesh","home-page.next.business.capacity.visual.lane.2.body":"Dweve-operated public Mesh capacity","home-page.next.business.capacity.visual.lane.2.state":"Regional route","home-page.next.business.capacity.visual.lane.3.title":"Isolated capacity","home-page.next.business.capacity.visual.lane.3.body":"No outbound network path","home-page.next.business.capacity.visual.lane.3.state":"High-control route","home-page.next.business.capacity.visual.rule.label":"Decision rule","home-page.next.business.capacity.visual.rule.value":"filter policy + risk -> rank cost + urgency","home-page.next.business.capacity.visual.rule.note":"Only eligible capacity enters the ranking","home-page.next.business.boundary.eyebrow":"Choose the operating perimeter","home-page.next.business.boundary.title.0":"Change the boundary","home-page.next.business.boundary.title.1":"without changing the workflow","home-page.next.business.boundary.body":"Keep the Fabric workflow familiar while moving from the Business Workspace on the public Mesh to licensed customer operation or a physically isolated perimeter. Location, product rights, network path, and operating responsibility change; sources, review, ownership, and approval remain recognisable.","home-page.next.business.boundary.pill.0":"Business Workspace","home-page.next.business.boundary.pill.1":"Private path","home-page.next.business.boundary.pill.2":"Isolated path","home-page.next.business.boundary.footer":"Risk posture changes, the workflow does not","home-page.next.business.boundary.side.title":"Deployment perimeter","home-page.next.business.boundary.side.tag":"BOUNDARY SET","home-page.next.business.boundary.side.0.label":"Business Workspace","home-page.next.business.boundary.side.0.value":"Managed in the selected region","home-page.next.business.boundary.side.1.label":"Private","home-page.next.business.boundary.side.1.value":"Customer-controlled network","home-page.next.business.boundary.side.2.label":"Isolated","home-page.next.business.boundary.side.2.value":"No outbound network route","home-page.next.business.boundary.side.3.label":"Constant","home-page.next.business.boundary.side.3.value":"Same review and approval path","home-page.next.business.boundary.side.foot":"One workflow across three perimeters","home-page.next.business.boundary.detail.label":"The boundary in plain terms","home-page.next.business.boundary.detail.0":"A region-managed Business Workspace, licensed customer operation, and physically isolated route change where data runs and who operates it. The three modes share one vocabulary while exposing different routes.","home-page.next.business.boundary.detail.1":"They do not change the work object or its review path. Sources, ownership, approval, and evidence stay recognisable across the perimeter choice, so moving the perimeter never asks a team to relearn the workflow.","home-page.next.business.boundary.visual.title":"Deployment perimeter","home-page.next.business.boundary.visual.status":"BOUNDARY SET","home-page.next.business.boundary.visual.foot":"One workflow across three perimeters","home-page.next.business.boundary.visual.core":"Same workflow and approvals","home-page.next.business.boundary.visual.zone.0.title":"Business Workspace","home-page.next.business.boundary.visual.zone.0.body":"Business Workspace on the public Mesh","home-page.next.business.boundary.visual.zone.0.state":"Available","home-page.next.business.boundary.visual.zone.1.title":"Private","home-page.next.business.boundary.visual.zone.1.body":"Customer-controlled network","home-page.next.business.boundary.visual.zone.1.state":"Available","home-page.next.business.boundary.visual.zone.2.title":"Isolated","home-page.next.business.boundary.visual.zone.2.body":"No outbound network route","home-page.next.business.boundary.visual.zone.2.state":"Available","home-page.next.business.boundary.visual.constant.label":"What remains constant","home-page.next.business.boundary.visual.constant.value":"Sources, review, owner, approval","home-page.next.business.evidence.eyebrow":"Evidence in the flow","home-page.next.business.evidence.title.0":"Build the audit packet","home-page.next.business.evidence.title.1":"while work happens","home-page.next.business.evidence.body":"Fabric attaches the source version, applied rule, reviewer, exception, approval, and resulting action as work moves. Audits, incident reviews, and customer questions start from the recorded path, with facts separated from human judgement.","home-page.next.business.evidence.pill.0":"Built in flow","home-page.next.business.evidence.pill.1":"Exact versions","home-page.next.business.evidence.pill.2":"Judgement named","home-page.next.business.evidence.footer":"The packet keeps source version, applied rule, reviewer, approval, and action together","home-page.next.business.evidence.side.title":"Audit packet","home-page.next.business.evidence.side.tag":"BUILT DURING WORK","home-page.next.business.evidence.side.0.label":"Source version","home-page.next.business.evidence.side.0.value":"Exact material remains attached","home-page.next.business.evidence.side.1.label":"Applied rule","home-page.next.business.evidence.side.1.value":"Governing rule named in context","home-page.next.business.evidence.side.2.label":"Judgement","home-page.next.business.evidence.side.2.value":"Reviewer and exception identified","home-page.next.business.evidence.side.3.label":"Packet","home-page.next.business.evidence.side.3.value":"Full path built during work","home-page.next.business.evidence.side.foot":"Evidence arrives with the decision","home-page.next.business.evidence.detail.label":"The record it leaves","home-page.next.business.evidence.detail.0":"The packet keeps the source version, rule, reviewer, exception, approval, and resulting action close to the work that produced them. It is assembled while the work runs rather than gathered afterwards.","home-page.next.business.evidence.detail.1":"That makes an audit or incident review a read of the recorded path, not a reconstruction from memory, inboxes, and unlabelled copies. The exact versions that were used are named, so the review starts from them.","home-page.next.business.evidence.visual.title":"Audit packet","home-page.next.business.evidence.visual.status":"BUILT DURING WORK","home-page.next.business.evidence.visual.foot":"Evidence arrives with the decision","home-page.next.business.evidence.visual.packet.title":"Decision packet","home-page.next.business.evidence.visual.packet.id":"Current","home-page.next.business.evidence.visual.file.0.name":"source-version.json","home-page.next.business.evidence.visual.file.0.meta":"Source and version","home-page.next.business.evidence.visual.file.1.name":"applied-rule.txt","home-page.next.business.evidence.visual.file.1.meta":"Applied rule","home-page.next.business.evidence.visual.file.2.name":"review.json","home-page.next.business.evidence.visual.file.2.meta":"Review and exception","home-page.next.business.evidence.visual.file.3.name":"approval.json","home-page.next.business.evidence.visual.file.3.meta":"Approval and action","home-page.next.business.evidence.visual.event.0.title":"Intake","home-page.next.business.evidence.visual.event.0.body":"Request captured","home-page.next.business.evidence.visual.event.1.title":"Evidence","home-page.next.business.evidence.visual.event.1.body":"Versions fixed","home-page.next.business.evidence.visual.event.2.title":"Review","home-page.next.business.evidence.visual.event.2.body":"Judgement recorded","home-page.next.business.evidence.visual.event.3.title":"Decision","home-page.next.business.evidence.visual.event.3.body":"Packet finalised","home-page.next.business.adoption.eyebrow":"Prove before you expand","home-page.next.business.adoption.title.0":"Begin with one workflow","home-page.next.business.adoption.title.1":"and measure the gain","home-page.next.business.adoption.body":"Choose real work with a named owner and a decision that matters. Baseline cycle time, queue age, repeat work, exceptions, and evidence effort; then run the same workflow in Fabric. Expand only after the agreed measures improve, reusing the same objects and contracts.","home-page.next.business.adoption.pill.0":"Real workload","home-page.next.business.adoption.pill.1":"Known baseline","home-page.next.business.adoption.pill.2":"Measured gain","home-page.next.business.adoption.footer":"Adoption follows evidence, not enthusiasm","home-page.next.business.adoption.side.title":"Adoption path","home-page.next.business.adoption.side.tag":"BASELINE FIRST","home-page.next.business.adoption.side.0.label":"First workflow","home-page.next.business.adoption.side.0.value":"Real work, clear owner","home-page.next.business.adoption.side.1.label":"Baseline","home-page.next.business.adoption.side.1.value":"Time, rework, exceptions, evidence","home-page.next.business.adoption.side.2.label":"Proof","home-page.next.business.adoption.side.2.value":"Compare like with like","home-page.next.business.adoption.side.3.label":"Expansion","home-page.next.business.adoption.side.3.value":"Add teams in measured stages","home-page.next.business.adoption.side.foot":"Expansion follows measured gain","home-page.next.business.adoption.detail.label":"The proof before scale","home-page.next.business.adoption.detail.0":"Choose work that already happens, name the owner, and agree which measures describe a better run before changing the operating path. A known baseline is what makes the later comparison worth reading at all.","home-page.next.business.adoption.detail.1":"The same objects and contracts then carry the comparison into adjacent teams. Expansion follows evidence, not a promise made by the first demonstration, and the second workflow reuses the path the first one proved.","home-page.next.business.adoption.visual.title":"Adoption path","home-page.next.business.adoption.visual.status":"PROOF ACTIVE","home-page.next.business.adoption.visual.foot":"Expansion follows measured gain","home-page.next.business.adoption.visual.lane":"Rollout lane","home-page.next.business.adoption.visual.period.0":"Start","home-page.next.business.adoption.visual.period.1":"Prove","home-page.next.business.adoption.visual.period.2":"Extend","home-page.next.business.adoption.visual.period.3":"Operate","home-page.next.business.adoption.visual.lane.0.title":"Real workflow","home-page.next.business.adoption.visual.lane.0.cell.0":"Intake","home-page.next.business.adoption.visual.lane.0.cell.1":"Sources","home-page.next.business.adoption.visual.lane.0.cell.2":"Review","home-page.next.business.adoption.visual.lane.0.cell.3":"Approval","home-page.next.business.adoption.visual.lane.1.title":"Adjacent teams","home-page.next.business.adoption.visual.lane.1.cell.0":"Owner","home-page.next.business.adoption.visual.lane.1.cell.1":"Access","home-page.next.business.adoption.visual.lane.1.cell.2":"Shared path","home-page.next.business.adoption.visual.lane.1.cell.3":"Active","home-page.next.business.adoption.visual.lane.2.title":"Wider operation","home-page.next.business.adoption.visual.lane.2.cell.0":"Baseline","home-page.next.business.adoption.visual.lane.2.cell.1":"Records","home-page.next.business.adoption.visual.lane.2.cell.2":"Deployment","home-page.next.business.adoption.visual.lane.2.cell.3":"Extended","home-page.next.business.adoption.visual.gate.label":"Expansion gate","home-page.next.business.adoption.visual.gate.value":"First workflow clears agreed measures","home-page.next.business.ownership.eyebrow":"Set responsibility early","home-page.next.business.ownership.title.0":"Know who controls what","home-page.next.business.ownership.title.1":"and how to leave","home-page.next.business.ownership.body":"Dweve maintains the product, contracts, and agreed support. The customer controls data, access, policy, reviewers, deployment, and exit. Exportable work and records keep operating history usable if the relationship changes.","home-page.next.business.ownership.pill.0":"We maintain","home-page.next.business.ownership.pill.1":"You control","home-page.next.business.ownership.pill.2":"History exports","home-page.next.business.ownership.footer":"Roles and exit are clear before rollout","home-page.next.business.ownership.side.title":"Responsibility map","home-page.next.business.ownership.side.tag":"ROLES AGREED","home-page.next.business.ownership.side.0.label":"Dweve carries","home-page.next.business.ownership.side.0.value":"Product, contracts, agreed support","home-page.next.business.ownership.side.1.label":"Customer governs","home-page.next.business.ownership.side.1.value":"Access, policy, reviewers, decisions","home-page.next.business.ownership.side.2.label":"Customer retains","home-page.next.business.ownership.side.2.value":"Data, records, deployment choice","home-page.next.business.ownership.side.3.label":"Exit","home-page.next.business.ownership.side.3.value":"Export preserves operating history","home-page.next.business.ownership.side.foot":"Control stays explicit","home-page.next.business.ownership.detail.label":"The handover rule","home-page.next.business.ownership.detail.0":"Dweve carries the product, contracts, and agreed support. The customer keeps authority over data, access, policy, reviewers, and deployment. Which side holds which decision is written down rather than assumed.","home-page.next.business.ownership.detail.1":"Exportable work and records make the operating history usable beyond a single relationship, so leaving is a defined path rather than an assumption. The history leaves in a form that still reads as the work it describes.","home-page.next.business.ownership.visual.title":"Responsibility map","home-page.next.business.ownership.visual.status":"ROLES AGREED","home-page.next.business.ownership.visual.foot":"Control stays explicit","home-page.next.business.ownership.visual.column.0.title":"Dweve carries","home-page.next.business.ownership.visual.column.0.row.0.title":"Product","home-page.next.business.ownership.visual.column.0.row.0.body":"Maintained surface","home-page.next.business.ownership.visual.column.0.row.1.title":"Contracts","home-page.next.business.ownership.visual.column.0.row.1.body":"Interfaces and formats","home-page.next.business.ownership.visual.column.0.row.2.title":"Support","home-page.next.business.ownership.visual.column.0.row.2.body":"Agreed scope","home-page.next.business.ownership.visual.column.0.row.3.title":"Updates","home-page.next.business.ownership.visual.column.0.row.3.body":"Supported changes","home-page.next.business.ownership.visual.column.1.title":"Customer controls","home-page.next.business.ownership.visual.column.1.row.0.title":"Data","home-page.next.business.ownership.visual.column.1.row.0.body":"Data and sources","home-page.next.business.ownership.visual.column.1.row.1.title":"Records","home-page.next.business.ownership.visual.column.1.row.1.body":"History and approvals","home-page.next.business.ownership.visual.column.1.row.2.title":"Deployment","home-page.next.business.ownership.visual.column.1.row.2.body":"Business Workspace, licensed, isolated","home-page.next.business.ownership.visual.column.1.row.3.title":"Exit","home-page.next.business.ownership.visual.column.1.row.3.body":"Export and transition","home-page.next.business.ownership.visual.exit.label":"Exit","home-page.next.business.ownership.visual.exit.value":"Work and records export","home-page.next.technical.request.eyebrow":"One request, one trace","home-page.next.technical.request.title.0":"Follow the request","home-page.next.technical.request.title.1":"and keep every hop","home-page.next.technical.request.body":"Fabric owns the durable work object and the returned result. A route can call Nexus for multi-agent coordination or Aura for software change, Loom for cognition, Spindle for versioned knowledge, Charter and Lattice for explicit constraints, and Kera, Core, or Mesh only when target compilation, execution, or placement is required. The trace records the boundaries that ran and the ones the route did not need.","home-page.next.technical.request.pill.0":"Typed request","home-page.next.technical.request.pill.1":"Explicit hops","home-page.next.technical.request.pill.2":"Returned trace","home-page.next.technical.request.footer":"Output and producing path return together","home-page.next.technical.request.side.title":"Request trace","home-page.next.technical.request.side.tag":"TRACE ATTACHED","home-page.next.technical.request.side.0.label":"Work boundary","home-page.next.technical.request.side.0.value":"Fabric owns context and result","home-page.next.technical.request.side.1.label":"Agent path","home-page.next.technical.request.side.1.value":"Nexus or Aura coordinates actors","home-page.next.technical.request.side.2.label":"Cognitive graph","home-page.next.technical.request.side.2.value":"Loom composes; Spindle versions knowledge","home-page.next.technical.request.side.3.label":"Execution return","home-page.next.technical.request.side.3.value":"Target, execution, and placement stay optional","home-page.next.technical.request.side.foot":"Output returns with its path","home-page.next.technical.request.detail.label":"The contract at the edge","home-page.next.technical.request.detail.0":"Fabric owns the durable work object and returns the result to that same boundary. Components participate through named interfaces instead of taking the caller's state with them.","home-page.next.technical.request.detail.1":"The trace records both the hops that ran and the boundaries the route skipped. That distinction is part of the result, not an after-the-fact explanation. A route that never reached compilation, execution, or placement says so.","home-page.next.technical.request.visual.title":"Request trace","home-page.next.technical.request.visual.status":"TRACE COMPLETE","home-page.next.technical.request.visual.foot":"Output returns with its path","home-page.next.technical.request.visual.command":"fabric run decision-review","home-page.next.technical.request.visual.run":"trace on","home-page.next.technical.request.visual.trace.0.node":"Fabric","home-page.next.technical.request.visual.trace.0.event":"work object","home-page.next.technical.request.visual.trace.1.node":"Nexus / Aura","home-page.next.technical.request.visual.trace.1.event":"agent route, when needed","home-page.next.technical.request.visual.trace.2.node":"Loom / Spindle","home-page.next.technical.request.visual.trace.2.event":"cognition + knowledge","home-page.next.technical.request.visual.trace.3.node":"Charter / Lattice","home-page.next.technical.request.visual.trace.3.event":"constraints evaluated","home-page.next.technical.request.visual.trace.4.node":"Kera","home-page.next.technical.request.visual.trace.4.event":"optional target emitted","home-page.next.technical.request.visual.trace.5.node":"Core / Mesh","home-page.next.technical.request.visual.trace.5.event":"execution + placement","home-page.next.technical.request.visual.trace.6.node":"Fabric","home-page.next.technical.request.visual.trace.6.event":"result + trace","home-page.next.technical.request.visual.result.label":"Return value","home-page.next.technical.request.visual.result.value":"result + route + source + policy + execution + approval","home-page.next.technical.replay.eyebrow":"Observe the whole run","home-page.next.technical.replay.title.0":"Replay the path","home-page.next.technical.replay.title.1":"from request to receipt","home-page.next.technical.replay.body":"A replay starts from the Fabric work ID and walks source versions, policy artifacts, agent transitions, graph and target events, and the returned receipt in order. It reconstructs the recorded path; deterministic components can re-execute when inputs, artifacts, and mode are pinned. It does not establish external truth.","home-page.next.technical.replay.pill.0":"Ordered events","home-page.next.technical.replay.pill.1":"Pinned artifacts","home-page.next.technical.replay.pill.2":"Final receipt","home-page.next.technical.replay.footer":"The replay shows each event and the evidence returned with it","home-page.next.technical.replay.side.title":"Replay boundary","home-page.next.technical.replay.side.tag":"PATH RECORDED","home-page.next.technical.replay.side.0.label":"Request","home-page.next.technical.replay.side.0.value":"Work ID and input hash","home-page.next.technical.replay.side.1.label":"Evidence","home-page.next.technical.replay.side.1.value":"Source versions and applied rule","home-page.next.technical.replay.side.2.label":"Runtime","home-page.next.technical.replay.side.2.value":"Agent transitions and execution target","home-page.next.technical.replay.side.3.label":"Receipt","home-page.next.technical.replay.side.3.value":"Result, approval, and event links","home-page.next.technical.replay.side.foot":"Recorded path, bounded claim","home-page.next.technical.replay.detail.label":"Replay with limits","home-page.next.technical.replay.detail.0":"A replay follows the work ID, source versions, policy outcome, agent transitions, target events, and returned receipt in the recorded order. That order is the one the run produced, not a sequence assembled at read time.","home-page.next.technical.replay.detail.1":"Pinned inputs let deterministic components run again, but replay reconstructs the recorded path; it does not establish external truth. It tells you what the system did, and nothing about the world outside it.","home-page.next.technical.replay.visual.title":"End-to-end replay","home-page.next.technical.replay.visual.status":"RECEIPT VERIFIED","home-page.next.technical.replay.visual.foot":"Six events from request to receipt","home-page.next.technical.replay.visual.event.0.node":"Fabric","home-page.next.technical.replay.visual.event.0.action":"request.created","home-page.next.technical.replay.visual.event.0.evidence":"work ID + input hash","home-page.next.technical.replay.visual.event.1.node":"Spindle","home-page.next.technical.replay.visual.event.1.action":"sources.resolved","home-page.next.technical.replay.visual.event.1.evidence":"atom IDs + source versions","home-page.next.technical.replay.visual.event.2.node":"Charter / Lattice","home-page.next.technical.replay.visual.event.2.action":"policy.evaluated","home-page.next.technical.replay.visual.event.2.evidence":"rule artifact + outcome","home-page.next.technical.replay.visual.event.3.node":"Nexus / Aura","home-page.next.technical.replay.visual.event.3.action":"agent.transition","home-page.next.technical.replay.visual.event.3.evidence":"node + capability + state","home-page.next.technical.replay.visual.event.4.node":"Kera / Core","home-page.next.technical.replay.visual.event.4.action":"execution.completed","home-page.next.technical.replay.visual.event.4.evidence":"graph ID + target + result hash","home-page.next.technical.replay.visual.event.5.node":"Fabric / Ledger","home-page.next.technical.replay.visual.event.5.action":"receipt.attached","home-page.next.technical.replay.visual.event.5.evidence":"event links + approval","home-page.next.technical.replay.visual.receipt.label":"Run receipt","home-page.next.technical.replay.visual.receipt.id":"receipt:decision-review","home-page.next.technical.replay.visual.receipt.state":"CHAIN COMPLETE","home-page.next.technical.stack.eyebrow":"Architecture by responsibility","home-page.next.technical.stack.title.0":"Map each responsibility","home-page.next.technical.stack.title.1":"then inspect the handoffs","home-page.next.technical.stack.body":"Five responsibility bands explain where work happens without pretending every product is a separate architectural layer. Product surfaces call coordination, cognition, state, and compute through named handoffs. Mesh defines where that system may run.","home-page.next.technical.stack.pill.0":"Five responsibility bands","home-page.next.technical.stack.pill.1":"Named handoffs","home-page.next.technical.stack.pill.2":"Placement envelope","home-page.next.technical.stack.footer":"Responsibilities are grouped; every boundary remains inspectable","home-page.next.technical.stack.side.title":"System responsibility map","home-page.next.technical.stack.side.tag":"SYSTEM MAP","home-page.next.technical.stack.side.0.label":"Surfaces","home-page.next.technical.stack.side.0.value":"Operational product capabilities","home-page.next.technical.stack.side.1.label":"Runtime layers","home-page.next.technical.stack.side.1.value":"Graphs, state, and execution","home-page.next.technical.stack.side.2.label":"Foundations","home-page.next.technical.stack.side.2.value":"Inspectable behavior and formats","home-page.next.technical.stack.side.3.label":"Dependency rule","home-page.next.technical.stack.side.3.value":"Edges point down, without hidden cycles","home-page.next.technical.stack.side.foot":"Every boundary stays named","home-page.next.technical.stack.visual.title":"Responsibility and handoff map","home-page.next.technical.stack.visual.status":"RESPONSIBILITIES MAPPED","home-page.next.technical.stack.visual.foot":"Every handoff stays named","home-page.next.technical.stack.visual.band.0.name":"Product surfaces","home-page.next.technical.stack.visual.band.0.role":"Where people and organisations direct work","home-page.next.technical.stack.visual.band.0.products":"Fabric · Charter","home-page.next.technical.stack.visual.band.0.contract":"intent → governed work","home-page.next.technical.stack.visual.band.1.name":"Coordination","home-page.next.technical.stack.visual.band.1.role":"Routes people, agents, and shared knowledge","home-page.next.technical.stack.visual.band.1.products":"Nexus · Aura · Spindle","home-page.next.technical.stack.visual.band.1.contract":"plan → supervised action","home-page.next.technical.stack.visual.band.2.name":"Cognition","home-page.next.technical.stack.visual.band.2.role":"Selects and combines specialist reasoning","home-page.next.technical.stack.visual.band.2.products":"Loom","home-page.next.technical.stack.visual.band.2.contract":"context → proposed result","home-page.next.technical.stack.visual.band.3.name":"State and evidence","home-page.next.technical.stack.visual.band.3.role":"Keeps meaning, policy, time, and provenance","home-page.next.technical.stack.visual.band.3.products":"BitWeave · Lattice · AION · Twin","home-page.next.technical.stack.visual.band.3.contract":"event → attributable state","home-page.next.technical.stack.visual.band.4.name":"Compute foundations","home-page.next.technical.stack.visual.band.4.role":"Compiles and executes the work","home-page.next.technical.stack.visual.band.4.products":"Core · Kera · Reed · Numerus","home-page.next.technical.stack.visual.band.4.contract":"typed program → execution","home-page.next.technical.stack.visual.placement.name":"Mesh placement envelope","home-page.next.technical.stack.visual.placement.role":"Constrains where every responsibility may execute","home-page.next.technical.stack.visual.placement.contract":"device · private cluster · European region","home-page.next.technical.stack.visual.group.0.title":"Foundations","home-page.next.technical.stack.visual.group.0.row.0.name":"L01 Silicon","home-page.next.technical.stack.visual.group.0.row.0.role":"Target hardware","home-page.next.technical.stack.visual.group.0.row.1.name":"L02 Numerus","home-page.next.technical.stack.visual.group.0.row.1.role":"Arithmetic contract","home-page.next.technical.stack.visual.group.0.row.2.name":"L03 Reed and Kera","home-page.next.technical.stack.visual.group.0.row.2.role":"Syntax + graph","home-page.next.technical.stack.visual.group.0.row.3.name":"L04 Core","home-page.next.technical.stack.visual.group.0.row.3.role":"Execution","home-page.next.technical.stack.visual.group.1.title":"State + control","home-page.next.technical.stack.visual.group.1.row.0.name":"L05 BitWeave","home-page.next.technical.stack.visual.group.1.row.0.role":"Retrieval","home-page.next.technical.stack.visual.group.1.row.1.name":"L06 Lattice and AION","home-page.next.technical.stack.visual.group.1.row.1.role":"Policy + attestation","home-page.next.technical.stack.visual.group.1.row.2.name":"L07 Twin","home-page.next.technical.stack.visual.group.1.row.2.role":"State","home-page.next.technical.stack.visual.group.1.row.3.name":"L08 Loom","home-page.next.technical.stack.visual.group.1.row.3.role":"Cognitive graph","home-page.next.technical.stack.visual.group.2.title":"Surfaces + placement","home-page.next.technical.stack.visual.group.2.row.0.name":"L09 Nexus and Aura","home-page.next.technical.stack.visual.group.2.row.0.role":"Agent runtime","home-page.next.technical.stack.visual.group.2.row.1.name":"L10 Spindle","home-page.next.technical.stack.visual.group.2.row.1.role":"Knowledge state","home-page.next.technical.stack.visual.group.2.row.2.name":"L11 Fabric","home-page.next.technical.stack.visual.group.2.row.2.role":"Workspace graph","home-page.next.technical.stack.visual.group.2.row.3.name":"L12 Mesh","home-page.next.technical.stack.visual.group.2.row.3.role":"Placement","home-page.next.technical.stack.visual.contract.label":"Dependency rule","home-page.next.technical.stack.visual.contract.value":"typed input → explicit output → preserved invariant","home-page.next.technical.foundations.eyebrow":"Below the product surfaces","home-page.next.technical.foundations.title.0":"Inspect the foundations","home-page.next.technical.foundations.title.1":"through their real contracts","home-page.next.technical.foundations.body":"The production open catalogue contains fourteen foundations with distinct jobs, from deterministic arithmetic and parsing to simulation, proof, records, data exchange, document handling, collection, and prompt compression. Jacquard remains adjacent research, not a production dependency. Inspect the semantics at each handoff before replacing a layer.","home-page.next.technical.foundations.pill.0":"Concrete formats","home-page.next.technical.foundations.pill.1":"Named invariants","home-page.next.technical.foundations.pill.2":"Directed deps","home-page.next.technical.foundations.footer":"Each handoff exposes its interface and invariant for inspection","home-page.next.technical.foundations.side.title":"Inspection path","home-page.next.technical.foundations.side.tag":"SEMANTICS EXPLICIT","home-page.next.technical.foundations.side.0.label":"Input shape","home-page.next.technical.foundations.side.0.value":"Types, grammar, state, or premises","home-page.next.technical.foundations.side.1.label":"Interface","home-page.next.technical.foundations.side.1.value":"API, ABI, or portable format","home-page.next.technical.foundations.side.2.label":"Invariant","home-page.next.technical.foundations.side.2.value":"Behavior a replacement must preserve","home-page.next.technical.foundations.side.3.label":"Conformance","home-page.next.technical.foundations.side.3.value":"Test substitution at the boundary","home-page.next.technical.foundations.side.foot":"Inspect the handoff, not the brand","home-page.next.technical.foundations.detail.label":"The replacement test","home-page.next.technical.foundations.detail.0":"Each foundation exposes an interface and an invariant: a format, state transition, proof relation, or execution result that the next layer can inspect. Nothing at that seam is left to convention.","home-page.next.technical.foundations.detail.1":"A replacement is acceptable only when it preserves that contract under the same input and declared conditions. The product name is not the interface, and conformance is demonstrated rather than asserted.","home-page.next.technical.foundations.visual.title":"Foundation contracts","home-page.next.technical.foundations.visual.status":"OPEN CATALOGUE MAPPED","home-page.next.technical.foundations.visual.foot":"Interfaces carry semantics upward","home-page.next.technical.foundations.visual.foundation.0.name":"Numerus","home-page.next.technical.foundations.visual.foundation.0.interface":"Q-format / Decimal / AXIOM","home-page.next.technical.foundations.visual.foundation.0.invariant":"Numeric profile fixes semantics","home-page.next.technical.foundations.visual.foundation.1.name":"Reed","home-page.next.technical.foundations.visual.foundation.1.interface":"Rust API / CLI / LSP / C ABI","home-page.next.technical.foundations.visual.foundation.1.invariant":"Tree bound to input + grammar","home-page.next.technical.foundations.visual.foundation.2.name":"BitWeave","home-page.next.technical.foundations.visual.foundation.2.interface":".bwks / Rust / C / Python","home-page.next.technical.foundations.visual.foundation.2.invariant":"Same state, same ordered result","home-page.next.technical.foundations.visual.foundation.3.name":"Lattice","home-page.next.technical.foundations.visual.foundation.3.interface":"mmap artifact / Rust / C / WASM","home-page.next.technical.foundations.visual.foundation.3.invariant":"Same artifact, same answer","home-page.next.technical.foundations.visual.foundation.4.name":"Twin","home-page.next.technical.foundations.visual.foundation.4.interface":"typed events / append / fold / replay","home-page.next.technical.foundations.visual.foundation.4.invariant":"Canonical log, derived state","home-page.next.technical.foundations.visual.foundation.5.name":"FMI","home-page.next.technical.foundations.visual.foundation.5.interface":"FMI 3.0 / model exchange / co-simulation","home-page.next.technical.foundations.visual.foundation.5.invariant":"Pinned model state replays deterministically","home-page.next.technical.foundations.visual.foundation.6.name":"AION","home-page.next.technical.foundations.visual.foundation.6.interface":"SMT API / LRAT / DRAT / Alethe","home-page.next.technical.foundations.visual.foundation.6.invariant":"Solver result and proof stay tied to premises","home-page.next.technical.foundations.visual.rule.label":"Dependency rule","home-page.next.technical.foundations.visual.rule.value":"higher layer -> declared interface -> foundation","home-page.next.technical.workspace-graph.eyebrow":"A durable work boundary","home-page.next.technical.workspace-graph.title.0":"Keep the work graph","home-page.next.technical.workspace-graph.title.1":"stable across providers","home-page.next.technical.workspace-graph.body":"Fabric makes the workspace object graph the durable boundary. Goals, sources, participants, tools, approvals, events, and records belong to the work, not a provider conversation. Models and services connect through typed adapters, so a backend can change without moving state or losing execution history.","home-page.next.technical.workspace-graph.pill.0":"Object graph","home-page.next.technical.workspace-graph.pill.1":"Typed adapters","home-page.next.technical.workspace-graph.pill.2":"Retained history","home-page.next.technical.workspace-graph.footer":"The workspace graph retains state and execution history as providers change","home-page.next.technical.workspace-graph.side.title":"Fabric object graph","home-page.next.technical.workspace-graph.side.tag":"DURABLE GRAPH","home-page.next.technical.workspace-graph.side.0.label":"Center","home-page.next.technical.workspace-graph.side.0.value":"Workspace objects hold state","home-page.next.technical.workspace-graph.side.1.label":"Provider edge","home-page.next.technical.workspace-graph.side.1.value":"Backends use typed adapters","home-page.next.technical.workspace-graph.side.2.label":"Shared domain","home-page.next.technical.workspace-graph.side.2.value":"Interface, API, and runtime share it","home-page.next.technical.workspace-graph.side.3.label":"Change boundary","home-page.next.technical.workspace-graph.side.3.value":"Swap providers without moving state","home-page.next.technical.workspace-graph.side.foot":"The work owns its state","home-page.next.technical.workspace-graph.detail.label":"What stays durable","home-page.next.technical.workspace-graph.detail.0":"Goals, sources, participants, tools, approvals, events, and records belong to the workspace graph, not to a provider conversation. That graph is what a later reader opens, whatever produced the answer.","home-page.next.technical.workspace-graph.detail.1":"Typed adapters let a backend change at the edge while the work keeps its identity and execution history. The graph is the boundary that survives the swap, so history is retained across it rather than restarted by it.","home-page.next.technical.workspace-graph.visual.title":"Fabric object graph","home-page.next.technical.workspace-graph.visual.status":"DURABLE BOUNDARY","home-page.next.technical.workspace-graph.visual.foot":"The work owns its state","home-page.next.technical.workspace-graph.visual.root.title":"Fabric workspace","home-page.next.technical.workspace-graph.visual.root.body":"Durable work graph","home-page.next.technical.workspace-graph.visual.node.0.title":"Goal","home-page.next.technical.workspace-graph.visual.node.0.body":"Objective + success","home-page.next.technical.workspace-graph.visual.node.1.title":"Sources","home-page.next.technical.workspace-graph.visual.node.1.body":"Versioned material","home-page.next.technical.workspace-graph.visual.node.2.title":"Participants","home-page.next.technical.workspace-graph.visual.node.2.body":"People, agents, tools","home-page.next.technical.workspace-graph.visual.node.3.title":"Approvals","home-page.next.technical.workspace-graph.visual.node.3.body":"Authority + review","home-page.next.technical.workspace-graph.visual.node.4.title":"Activity","home-page.next.technical.workspace-graph.visual.node.4.body":"Trace events","home-page.next.technical.workspace-graph.visual.node.5.title":"Records","home-page.next.technical.workspace-graph.visual.node.5.body":"Result history","home-page.next.technical.workspace-graph.visual.boundary":"workspace.graph","home-page.next.technical.workspace-graph.visual.boundary.note":"Providers connect through typed adapters","home-page.next.technical.agents.eyebrow":"Agents as runtime nodes","home-page.next.technical.agents.title.0":"Give every agent","home-page.next.technical.agents.title.1":"a bounded contract","home-page.next.technical.agents.body":"Nexus and Aura model agents as governed runtime nodes. Each node has typed capabilities, scoped permissions, observable state, and a place in the task graph. Inputs, handovers, tool calls, retries, stops, and approvals become explicit transitions, so coordination can grow without sharing system-wide authority.","home-page.next.technical.agents.pill.0":"Typed capability","home-page.next.technical.agents.pill.1":"Scoped access","home-page.next.technical.agents.pill.2":"Observable state","home-page.next.technical.agents.footer":"Each node records identity, capabilities, permissions, and transitions","home-page.next.technical.agents.side.title":"Agent node contract","home-page.next.technical.agents.side.tag":"AUTHORITY BOUNDED","home-page.next.technical.agents.side.0.label":"Node identity","home-page.next.technical.agents.side.0.value":"Stable role in the graph","home-page.next.technical.agents.side.1.label":"Capabilities","home-page.next.technical.agents.side.1.value":"Typed functions define action","home-page.next.technical.agents.side.2.label":"Permissions","home-page.next.technical.agents.side.2.value":"Tools and paths stay scoped","home-page.next.technical.agents.side.3.label":"Transitions","home-page.next.technical.agents.side.3.value":"Handover, approval, failure","home-page.next.technical.agents.side.foot":"Authority stays local to the node","home-page.next.technical.agents.detail.label":"The runtime contract","home-page.next.technical.agents.detail.0":"An agent node is more than a prompt. Its identity, capabilities, permissions, state, and transitions are visible to the task graph around it, so nothing about the node stays implicit in a prompt string.","home-page.next.technical.agents.detail.1":"Handover, retry, stop, and approval are transitions with a place in the record. Coordination can grow without granting every node system-wide authority, because authority stays scoped to the node that needs it.","home-page.next.technical.agents.visual.title":"Agent node contract","home-page.next.technical.agents.visual.status":"AUTHORITY BOUNDED","home-page.next.technical.agents.visual.foot":"Authority stays local to the node","home-page.next.technical.agents.visual.state.0.title":"Registered","home-page.next.technical.agents.visual.state.0.body":"Identity + capability","home-page.next.technical.agents.visual.state.1.title":"Ready","home-page.next.technical.agents.visual.state.1.body":"Permissions loaded","home-page.next.technical.agents.visual.state.2.title":"Running","home-page.next.technical.agents.visual.state.2.body":"Bounded action active","home-page.next.technical.agents.visual.state.3.title":"Recorded","home-page.next.technical.agents.visual.state.3.body":"Result retained","home-page.next.technical.agents.visual.transition.0.event":"capability.bound","home-page.next.technical.agents.visual.transition.0.target":"Ready","home-page.next.technical.agents.visual.transition.1.event":"task.started","home-page.next.technical.agents.visual.transition.1.target":"Running","home-page.next.technical.agents.visual.transition.2.event":"approval.required","home-page.next.technical.agents.visual.transition.2.target":"Ready","home-page.next.technical.agents.visual.transition.3.event":"task.finished","home-page.next.technical.agents.visual.transition.3.target":"Recorded","home-page.next.technical.agents.visual.capability.0":"Typed input","home-page.next.technical.agents.visual.capability.1":"Scoped tools","home-page.next.technical.agents.visual.capability.2":"Visible state","home-page.next.technical.agents.visual.capability.3":"Explicit handover","home-page.next.technical.knowledge.eyebrow":"Knowledge with a lifecycle","home-page.next.technical.knowledge.title.0":"Version the knowledge","home-page.next.technical.knowledge.title.1":"without erasing history","home-page.next.technical.knowledge.body":"Spindle stores signed, versioned knowledge with source and transformation lineage. Corrections, withdrawals, policy changes, and conflicts are lifecycle events that identify affected atoms and exports. A signature establishes identity, integrity, and lineage, not truth; publication means that version passed its configured gates at that time.","home-page.next.technical.knowledge.pill.0":"Signed versions","home-page.next.technical.knowledge.pill.1":"Full lineage","home-page.next.technical.knowledge.pill.2":"Lifecycle events","home-page.next.technical.knowledge.footer":"Every version keeps its source, lineage, and lifecycle state","home-page.next.technical.knowledge.side.title":"Knowledge lifecycle","home-page.next.technical.knowledge.side.tag":"VERSION CURRENT","home-page.next.technical.knowledge.side.0.label":"Stable identity","home-page.next.technical.knowledge.side.0.value":"Each atom remains addressable","home-page.next.technical.knowledge.side.1.label":"Version state","home-page.next.technical.knowledge.side.1.value":"Changes append history","home-page.next.technical.knowledge.side.2.label":"Lineage graph","home-page.next.technical.knowledge.side.2.value":"Sources, transforms, dependants","home-page.next.technical.knowledge.side.3.label":"Claim boundary","home-page.next.technical.knowledge.side.3.value":"Integrity and lineage, not truth","home-page.next.technical.knowledge.side.foot":"History remains intact","home-page.next.technical.knowledge.detail.label":"The claim boundary","home-page.next.technical.knowledge.detail.0":"A signed version identifies the source and transformation path that produced it. Corrections and withdrawals append state instead of erasing the earlier record, so the earlier version stays addressable afterwards.","home-page.next.technical.knowledge.detail.1":"Publication means the configured gates passed for that version at that time. A signature supports integrity and lineage, not the truth of the claim itself. A conflict is a lifecycle event naming the atoms and exports it touches.","home-page.next.technical.knowledge.visual.title":"Knowledge lifecycle","home-page.next.technical.knowledge.visual.status":"VERSION CURRENT","home-page.next.technical.knowledge.visual.foot":"History remains intact","home-page.next.technical.knowledge.visual.passport.label":"Knowledge atom","home-page.next.technical.knowledge.visual.passport.id":"atom:policy/current","home-page.next.technical.knowledge.visual.passport.title":"Supplier retention rule","home-page.next.technical.knowledge.visual.passport.body":"Signed source + lineage","home-page.next.technical.knowledge.visual.field.0.label":"Identity","home-page.next.technical.knowledge.visual.field.0.value":"atom:retention-rule","home-page.next.technical.knowledge.visual.field.1.label":"Version","home-page.next.technical.knowledge.visual.field.1.value":"current","home-page.next.technical.knowledge.visual.field.2.label":"Source","home-page.next.technical.knowledge.visual.field.2.value":"vendor-policy.pdf","home-page.next.technical.knowledge.visual.field.3.label":"State","home-page.next.technical.knowledge.visual.field.3.value":"Gates passed","home-page.next.technical.knowledge.visual.lineage.0.title":"Captured","home-page.next.technical.knowledge.visual.lineage.0.body":"Source version retained","home-page.next.technical.knowledge.visual.lineage.1.title":"Structured","home-page.next.technical.knowledge.visual.lineage.1.body":"Claim + context split","home-page.next.technical.knowledge.visual.lineage.2.title":"Reviewed","home-page.next.technical.knowledge.visual.lineage.2.body":"Evidence gates applied","home-page.next.technical.knowledge.visual.lineage.3.title":"Published","home-page.next.technical.knowledge.visual.lineage.3.body":"Current version set","home-page.next.technical.model.eyebrow":"Cognition as a graph","home-page.next.technical.model.title.0":"Compose the cognition","home-page.next.technical.model.title.1":"and record every route","home-page.next.technical.model.body":"Loom composes perception, retrieval, memory, models, solvers, reasoning modes, and verifiers as typed specialist nodes. Task shape, capability, policy, evidence, and execution constraints select the route. The trace records activated and rejected branches with the constraints behind each choice.","home-page.next.technical.model.pill.0":"Typed specialists","home-page.next.technical.model.pill.1":"Explicit routing","home-page.next.technical.model.pill.2":"Route trace","home-page.next.technical.model.footer":"The graph records why each branch ran","home-page.next.technical.model.side.title":"Loom cognitive graph","home-page.next.technical.model.side.tag":"ROUTE RECORDED","home-page.next.technical.model.side.0.label":"Task shape","home-page.next.technical.model.side.0.value":"Request defines needed cognition","home-page.next.technical.model.side.1.label":"Specialist nodes","home-page.next.technical.model.side.1.value":"Methods keep typed outputs","home-page.next.technical.model.side.2.label":"Routing inputs","home-page.next.technical.model.side.2.value":"Policy and constraints select branches","home-page.next.technical.model.side.3.label":"Trace output","home-page.next.technical.model.side.3.value":"Activated and rejected paths","home-page.next.technical.model.side.foot":"Every route keeps its reason","home-page.next.technical.model.detail.label":"The route is the evidence","home-page.next.technical.model.detail.0":"Loom chooses specialist nodes from task shape, capability, policy, evidence, and execution constraints. The graph stays typed at each handoff, and each specialist is selected for a stated reason rather than by default.","home-page.next.technical.model.detail.1":"Activated and rejected branches remain visible with the constraints behind them, so a reviewer can challenge the route without guessing what ran. The route is the first piece of evidence a reviewer reads.","home-page.next.technical.model.visual.title":"Loom cognitive graph","home-page.next.technical.model.visual.status":"ROUTE RESOLVED","home-page.next.technical.model.visual.foot":"Every route keeps its reason","home-page.next.technical.model.visual.input.label":"Task","home-page.next.technical.model.visual.input.value":"Compare exception and propose route","home-page.next.technical.model.visual.router":"Resolve graph","home-page.next.technical.model.visual.specialist.0.title":"Perception","home-page.next.technical.model.visual.specialist.0.body":"Parse request + files","home-page.next.technical.model.visual.specialist.1.title":"Retrieval","home-page.next.technical.model.visual.specialist.1.body":"Find versioned sources","home-page.next.technical.model.visual.specialist.2.title":"Reasoning","home-page.next.technical.model.visual.specialist.2.body":"Evaluate constraints","home-page.next.technical.model.visual.specialist.3.title":"Verifier","home-page.next.technical.model.visual.specialist.3.body":"Check requirements","home-page.next.technical.model.visual.constraint.label":"Routing constraint","home-page.next.technical.model.visual.constraint.value":"policy + capability + evidence + budget","home-page.next.technical.model.visual.constraint.state":"Recorded","home-page.next.technical.execution.eyebrow":"Graph-preserving computation","home-page.next.technical.execution.title.0":"Lower the graph","home-page.next.technical.execution.title.1":"without losing its meaning","home-page.next.technical.execution.body":"Kera retains operations, types, shapes, effects, ownership, and memory policy while planning the whole graph and emitting for a target. Core supplies execution implementations across supported representations and backends. Dispatch, movement, and execution remain tied to graph semantics through target selection.","home-page.next.technical.execution.pill.0":"Typed graph","home-page.next.technical.execution.pill.1":"Whole-graph plan","home-page.next.technical.execution.pill.2":"Target emit","home-page.next.technical.execution.footer":"Target code retains the planned operation","home-page.next.technical.execution.side.title":"Execution lowering","home-page.next.technical.execution.side.tag":"SEMANTICS KEPT","home-page.next.technical.execution.side.0.label":"Graph semantics","home-page.next.technical.execution.side.0.value":"Type, shape, effects, ownership","home-page.next.technical.execution.side.1.label":"Graph plan","home-page.next.technical.execution.side.1.value":"Movement and execution together","home-page.next.technical.execution.side.2.label":"Target choice","home-page.next.technical.execution.side.2.value":"Emit follows machine contract","home-page.next.technical.execution.side.3.label":"Core path","home-page.next.technical.execution.side.3.value":"Implementation runs preserved operation","home-page.next.technical.execution.side.foot":"Meaning survives lowering","home-page.next.technical.execution.detail.label":"The lowering contract","home-page.next.technical.execution.detail.0":"Kera plans the graph with its operations, types, shapes, effects, ownership, and memory policy still attached to the work. Ownership and memory policy travel with the plan rather than being reintroduced at the target.","home-page.next.technical.execution.detail.1":"Core and its supported backends then execute the selected representation. Target choice changes the emitted path, not the operation the graph describes, so the same graph can be emitted elsewhere without a rewrite.","home-page.next.technical.execution.visual.title":"Execution lowering","home-page.next.technical.execution.visual.status":"SEMANTICS PRESERVED","home-page.next.technical.execution.visual.foot":"Meaning survives lowering","home-page.next.technical.execution.visual.stage.0.title":"Typed graph","home-page.next.technical.execution.visual.stage.0.body":"ops + shapes + effects","home-page.next.technical.execution.visual.stage.1.title":"Graph plan","home-page.next.technical.execution.visual.stage.1.body":"memory + movement","home-page.next.technical.execution.visual.stage.2.title":"Target emit","home-page.next.technical.execution.visual.stage.2.body":"semantics retained","home-page.next.technical.execution.visual.target.0.title":"CPU","home-page.next.technical.execution.visual.target.0.body":"Core path","home-page.next.technical.execution.visual.target.1.title":"GPU","home-page.next.technical.execution.visual.target.1.body":"Supported backend","home-page.next.technical.execution.visual.target.2.title":"WASM","home-page.next.technical.execution.visual.target.2.body":"Browser target","home-page.next.technical.execution.visual.target.3.title":"Isolated","home-page.next.technical.execution.visual.target.3.body":"Controlled target","home-page.next.technical.policy.eyebrow":"Policy inside the path","home-page.next.technical.policy.title.0":"Run policy in band","home-page.next.technical.policy.title.1":"and keep claims bounded","home-page.next.technical.policy.body":"Charter carries authority and policy beside the operating graph. Lattice evaluates explicit rules against supplied state and returns the applied path. AION is the SMT solver and proof platform: it solves bounded constraints against supplied premises and can emit portable proof material. None of these establish source truth, model quality, fairness, or legal compliance; those require separate evidence and judgement.","home-page.next.technical.policy.pill.0":"Policy attached","home-page.next.technical.policy.pill.1":"Portable proof","home-page.next.technical.policy.pill.2":"Claims bounded","home-page.next.technical.policy.footer":"The applied path records its rules, premises, and claim limits","home-page.next.technical.policy.side.title":"Policy and attestation","home-page.next.technical.policy.side.tag":"CLAIMS BOUNDED","home-page.next.technical.policy.side.0.label":"Charter carries","home-page.next.technical.policy.side.0.value":"Authority + policy","home-page.next.technical.policy.side.1.label":"Lattice checks","home-page.next.technical.policy.side.1.value":"Rules against supplied state","home-page.next.technical.policy.side.2.label":"AION establishes","home-page.next.technical.policy.side.2.value":"SMT result and proof follow premises","home-page.next.technical.policy.side.3.label":"Not established","home-page.next.technical.policy.side.3.value":"Truth, fairness, quality, compliance","home-page.next.technical.policy.side.foot":"Proof scope stays visible","home-page.next.technical.policy.detail.label":"What the proof does not say","home-page.next.technical.policy.detail.0":"Charter carries authority, Lattice evaluates rules against supplied state, and AION ties a solver result to its premises and proof material. Those three stay separable, so each can be inspected on its own terms.","home-page.next.technical.policy.detail.1":"Those records establish the applied path and its premises. They do not establish source truth, model quality, fairness, or legal compliance without separate evidence, and those remain matters for judgement.","home-page.next.technical.policy.visual.title":"Policy and attestation","home-page.next.technical.policy.visual.status":"CLAIM BOUNDARY VISIBLE","home-page.next.technical.policy.visual.foot":"Proof scope stays visible","home-page.next.technical.policy.visual.matrix.control":"Control","home-page.next.technical.policy.visual.matrix.head.0":"Charter","home-page.next.technical.policy.visual.matrix.head.1":"Lattice","home-page.next.technical.policy.visual.matrix.head.2":"AION","home-page.next.technical.policy.visual.matrix.row.0.title":"Authority","home-page.next.technical.policy.visual.matrix.row.1.title":"Rule path","home-page.next.technical.policy.visual.matrix.row.2.title":"State check","home-page.next.technical.policy.visual.matrix.row.3.title":"Premises","home-page.next.technical.policy.visual.matrix.row.4.title":"Deduction","home-page.next.technical.policy.visual.claim.label":"Established","home-page.next.technical.policy.visual.claim.value":"Rules and premises applied as recorded","home-page.next.technical.policy.visual.claim.note":"Not truth, fairness, quality, or compliance","home-page.next.technical.topology.eyebrow":"Topology as declared state","home-page.next.technical.topology.title.0":"Place work by contract","home-page.next.technical.topology.title.1":"and treat churn as normal","home-page.next.technical.topology.body":"Mesh declares eligible placement, capacity ownership, and trust and fault boundaries. The Business Workspace, licensed customer operation, and physically isolated modes share one vocabulary but expose different routes. Nodes may join, disappear, or yield to their owner; repartitioning and recovery treat that churn as topology state.","home-page.next.technical.topology.pill.0":"Placement rules","home-page.next.technical.topology.pill.1":"Owned capacity","home-page.next.technical.topology.pill.2":"Fault domains","home-page.next.technical.topology.footer":"Routes move while identity and perimeter stay explicit","home-page.next.technical.topology.side.title":"Mesh topology","home-page.next.technical.topology.side.tag":"TOPOLOGY DECLARED","home-page.next.technical.topology.side.0.label":"Placement contract","home-page.next.technical.topology.side.0.value":"Only eligible nodes receive work","home-page.next.technical.topology.side.1.label":"Capacity identity","home-page.next.technical.topology.side.1.value":"Resources remain tied to owners","home-page.next.technical.topology.side.2.label":"Fault boundary","home-page.next.technical.topology.side.2.value":"Failures stay inside trust domains","home-page.next.technical.topology.side.3.label":"Deployment mode","home-page.next.technical.topology.side.3.value":"Routes change, semantics do not","home-page.next.technical.topology.side.foot":"Placement remains explicit","home-page.next.technical.topology.detail.label":"Churn is part of the model","home-page.next.technical.topology.detail.0":"Mesh treats joining, leaving, yielding, and recovery as topology state. Placement remains constrained by eligibility, owner, trust, and fault boundaries. A node that yields to its owner is a state change, not a failure.","home-page.next.technical.topology.detail.1":"The route may change as capacity changes, but the work keeps its declared contract and perimeter. Repartitioning is observable state, not hidden scheduler behaviour, so operations can watch it happen.","home-page.next.technical.topology.visual.title":"Mesh topology","home-page.next.technical.topology.visual.status":"PLACEMENT RESOLVED","home-page.next.technical.topology.visual.foot":"Placement remains explicit","home-page.next.technical.topology.visual.control":"Placement + identity + faults","home-page.next.technical.topology.visual.node.0.title":"Managed Mesh node","home-page.next.technical.topology.visual.node.0.body":"Regional capacity","home-page.next.technical.topology.visual.node.1.title":"Private node","home-page.next.technical.topology.visual.node.1.body":"Customer network","home-page.next.technical.topology.visual.node.2.title":"Local node","home-page.next.technical.topology.visual.node.2.body":"Owner priority","home-page.next.technical.topology.visual.node.3.title":"Isolated node","home-page.next.technical.topology.visual.node.3.body":"No outbound path","home-page.next.technical.topology.visual.legend.0":"Eligible placement","home-page.next.technical.topology.visual.legend.1":"Capacity owner","home-page.next.technical.topology.visual.legend.2":"Fault boundary","home-page.next.technical.contracts.eyebrow":"Replaceability by contract","home-page.next.technical.contracts.title.0":"Replace one layer","home-page.next.technical.contracts.title.1":"without guessing behaviour","home-page.next.technical.contracts.body":"Typed inputs, versioned artifacts, stable formats, directed dependencies, and conformance checks define each boundary. Product surfaces depend on those contracts, not hidden shared state. A provider, engine, or service can be replaced one layer at a time and tested against observable behavior.","home-page.next.technical.contracts.pill.0":"Typed interfaces","home-page.next.technical.contracts.pill.1":"Stable formats","home-page.next.technical.contracts.pill.2":"Conformance","home-page.next.technical.contracts.footer":"A replacement must satisfy observable behavior","home-page.next.technical.contracts.side.title":"Replaceable boundary","home-page.next.technical.contracts.side.tag":"CONTRACT HELD","home-page.next.technical.contracts.side.0.label":"Interface first","home-page.next.technical.contracts.side.0.value":"Behavior defined at boundary","home-page.next.technical.contracts.side.1.label":"Artifacts","home-page.next.technical.contracts.side.1.value":"Versioned formats move across implementations","home-page.next.technical.contracts.side.2.label":"Dependencies","home-page.next.technical.contracts.side.2.value":"No hidden lower-layer state","home-page.next.technical.contracts.side.3.label":"Conformance","home-page.next.technical.contracts.side.3.value":"Observable behavior checked","home-page.next.technical.contracts.side.foot":"Replacement is testable","home-page.next.technical.contracts.detail.label":"The compatibility test","home-page.next.technical.contracts.detail.0":"Typed inputs, versioned artefacts, stable formats, and directed dependencies make a boundary inspectable before anyone swaps its implementation. A boundary you cannot inspect is not one you can safely replace.","home-page.next.technical.contracts.detail.1":"Conformance means the replacement accepts the same contract and preserves the observable behaviour. It does not require the same provider, engine, or internal state, because the test is the behaviour and nothing more.","home-page.next.technical.contracts.visual.title":"Replaceable boundary","home-page.next.technical.contracts.visual.status":"CONTRACT SATISFIED","home-page.next.technical.contracts.visual.foot":"Replacement is testable","home-page.next.technical.contracts.visual.table.surface":"Surface","home-page.next.technical.contracts.visual.table.now":"Current","home-page.next.technical.contracts.visual.table.next":"Replacement","home-page.next.technical.contracts.visual.table.held":"Held","home-page.next.technical.contracts.visual.row.0.surface":"Provider adapter","home-page.next.technical.contracts.visual.row.0.now":"Backend A","home-page.next.technical.contracts.visual.row.0.next":"Backend B","home-page.next.technical.contracts.visual.row.0.held":"Typed request","home-page.next.technical.contracts.visual.row.1.surface":"Knowledge store","home-page.next.technical.contracts.visual.row.1.now":"Spindle","home-page.next.technical.contracts.visual.row.1.next":"Conforming store","home-page.next.technical.contracts.visual.row.1.held":"Versioned lineage","home-page.next.technical.contracts.visual.row.2.surface":"Cognitive runtime","home-page.next.technical.contracts.visual.row.2.now":"Loom","home-page.next.technical.contracts.visual.row.2.next":"Conforming runtime","home-page.next.technical.contracts.visual.row.2.held":"Typed graph","home-page.next.technical.contracts.visual.row.3.surface":"Execution engine","home-page.next.technical.contracts.visual.row.3.now":"Core and Kera","home-page.next.technical.contracts.visual.row.3.next":"Conforming engine","home-page.next.technical.contracts.visual.row.3.held":"Target contract","home-page.next.technical.contracts.visual.row.4.surface":"Placement service","home-page.next.technical.contracts.visual.row.4.now":"Mesh","home-page.next.technical.contracts.visual.row.4.next":"Conforming service","home-page.next.technical.contracts.visual.row.4.held":"Placement contract","home-page.next.technical.contracts.visual.guarantee.label":"Conformance test","home-page.next.technical.contracts.visual.guarantee.value":"same input -> conforming behavior","home-page.next.consumer.workspace.eyebrow":"Inside Fabric","home-page.next.consumer.workspace.title.0":"Start with a real task","home-page.next.consumer.workspace.title.1":"and finish with a useful result","home-page.next.consumer.workspace.body":"Plan a day, compare an offer, understand a letter, prepare for an appointment, or turn notes into a checklist. Ask Fabric in your own words and keep the question, materials, choices, and result in one thread.","home-page.next.consumer.workspace.pill.0":"Plain language","home-page.next.consumer.workspace.pill.1":"Your materials","home-page.next.consumer.workspace.pill.2":"Usable result","home-page.next.consumer.workspace.footer":"Start with what you need done","home-page.next.consumer.workspace.side.title":"Fabric workspace","home-page.next.consumer.workspace.side.tag":"TASK OPEN","home-page.next.consumer.workspace.side.0.label":"Ask","home-page.next.consumer.workspace.side.0.value":"Use the words you know","home-page.next.consumer.workspace.side.1.label":"Add","home-page.next.consumer.workspace.side.1.value":"Bring useful files and notes","home-page.next.consumer.workspace.side.2.label":"Continue","home-page.next.consumer.workspace.side.2.value":"Keep the story in one thread","home-page.next.consumer.workspace.side.3.label":"Finish","home-page.next.consumer.workspace.side.3.value":"Leave with a usable result","home-page.next.consumer.workspace.side.foot":"One task, one thread","home-page.next.consumer.workspace.visual.title":"Fabric workspace","home-page.next.consumer.workspace.visual.status":"QUESTION OPEN","home-page.next.consumer.workspace.visual.foot":"One task, one thread","home-page.next.consumer.workspace.visual.folder.0.title":"Weekend plans","home-page.next.consumer.workspace.visual.folder.0.body":"Question + sources","home-page.next.consumer.workspace.visual.folder.1.title":"Saved places","home-page.next.consumer.workspace.visual.folder.1.body":"Notes + links","home-page.next.consumer.workspace.visual.folder.2.title":"Routines","home-page.next.consumer.workspace.visual.folder.2.body":"Saved patterns","home-page.next.consumer.workspace.visual.question.label":"Your question","home-page.next.consumer.workspace.visual.question.value":"Make a Saturday route from my saved places","home-page.next.consumer.workspace.visual.answer":"Museum first, then the harbour walk. Using your notes.","home-page.next.consumer.workspace.visual.source.0":"Rotterdam notes","home-page.next.consumer.workspace.visual.source.1":"Saved places","home-page.next.consumer.workspace.visual.sidebar.label":"Open thread","home-page.next.consumer.workspace.visual.sidebar.value":"3 materials · 1 result","home-page.next.consumer.workspace.visual.plan.0.time":"10:00","home-page.next.consumer.workspace.visual.plan.0.title":"Museum first","home-page.next.consumer.workspace.visual.plan.0.body":"Opening time checked","home-page.next.consumer.workspace.visual.plan.1.time":"12:30","home-page.next.consumer.workspace.visual.plan.1.title":"Courtyard lunch","home-page.next.consumer.workspace.visual.plan.1.body":"Saved preference kept","home-page.next.consumer.workspace.visual.plan.2.time":"14:15","home-page.next.consumer.workspace.visual.plan.2.title":"Harbour walk","home-page.next.consumer.workspace.visual.plan.2.body":"Route from your notes","home-page.next.consumer.workspace.visual.evidence.label":"Result assembled from","home-page.next.consumer.workspace.visual.evidence.value":"Rotterdam notes · saved places · opening time","home-page.next.consumer.workspace.visual.evidence.state":"Ready to keep","home-page.next.consumer.intake.eyebrow":"Add the useful pieces","home-page.next.consumer.intake.title.0":"Bring what you have","home-page.next.consumer.intake.title.1":"without sorting it first","home-page.next.consumer.intake.body":"Drop files, notes, messages, images, and links into Fabric. Names and previews stay visible, so you can see what is included, add a missing detail, or remove the wrong item before the next question.","home-page.next.consumer.intake.pill.0":"Files and images","home-page.next.consumer.intake.pill.1":"Notes and mail","home-page.next.consumer.intake.pill.2":"Links","home-page.next.consumer.intake.footer":"You do not need a perfect folder","home-page.next.consumer.intake.side.title":"Question materials","home-page.next.consumer.intake.side.tag":"CONTEXT READY","home-page.next.consumer.intake.side.0.label":"Add files","home-page.next.consumer.intake.side.0.value":"Names and previews stay visible","home-page.next.consumer.intake.side.1.label":"Add detail","home-page.next.consumer.intake.side.1.value":"Capture what only you know","home-page.next.consumer.intake.side.2.label":"Add links","home-page.next.consumer.intake.side.2.value":"Keep outside material nearby","home-page.next.consumer.intake.side.3.label":"Check","home-page.next.consumer.intake.side.3.value":"See what Fabric will use","home-page.next.consumer.intake.side.foot":"Messy input is welcome","home-page.next.consumer.intake.visual.title":"Question materials","home-page.next.consumer.intake.visual.status":"READY TO USE","home-page.next.consumer.intake.visual.foot":"Messy input is welcome","home-page.next.consumer.intake.visual.item.0.title":"Trip notes.pdf","home-page.next.consumer.intake.visual.item.0.body":"Dates + preferences","home-page.next.consumer.intake.visual.item.1.title":"Booking email","home-page.next.consumer.intake.visual.item.1.body":"Opening time","home-page.next.consumer.intake.visual.item.2.title":"Museum page","home-page.next.consumer.intake.visual.item.2.body":"Visitor details","home-page.next.consumer.intake.visual.item.3.title":"Map image","home-page.next.consumer.intake.visual.item.3.body":"Places marked","home-page.next.consumer.intake.visual.folder.title":"Weekend plan","home-page.next.consumer.intake.visual.folder.body":"Four items together","home-page.next.consumer.intake.visual.folder.state":"Ready to ask","home-page.next.consumer.sources.eyebrow":"Answers with sources","home-page.next.consumer.sources.title.0":"Open the source","home-page.next.consumer.sources.title.1":"and check the answer","home-page.next.consumer.sources.body":"Fabric shows which file supplied a date, which note carried a preference, and what still needs checking. Open the relevant passage beside the answer, then decide whether the result matches the material you gave it.","home-page.next.consumer.sources.pill.0":"Visible sources","home-page.next.consumer.sources.pill.1":"Exact passages","home-page.next.consumer.sources.pill.2":"Open beside answer","home-page.next.consumer.sources.footer":"Check the material, not the tone","home-page.next.consumer.sources.side.title":"Answer and sources","home-page.next.consumer.sources.side.tag":"SOURCES OPEN","home-page.next.consumer.sources.side.0.label":"Date","home-page.next.consumer.sources.side.0.value":"From your booking message","home-page.next.consumer.sources.side.1.label":"Place","home-page.next.consumer.sources.side.1.value":"From your saved list","home-page.next.consumer.sources.side.2.label":"Preference","home-page.next.consumer.sources.side.2.value":"From your own note","home-page.next.consumer.sources.side.3.label":"Unclear","home-page.next.consumer.sources.side.3.value":"Marked for your check","home-page.next.consumer.sources.side.foot":"Every detail has a place","home-page.next.consumer.sources.visual.title":"Answer and sources","home-page.next.consumer.sources.visual.status":"SOURCES ATTACHED","home-page.next.consumer.sources.visual.foot":"Every detail has a place","home-page.next.consumer.sources.visual.answer.label":"Suggested route","home-page.next.consumer.sources.visual.answer.body":"Museum, harbour walk, courtyard lunch","home-page.next.consumer.sources.visual.answer.confidence":"Sources attached","home-page.next.consumer.sources.visual.source.0.title":"Booking email","home-page.next.consumer.sources.visual.source.0.body":"Opening + tickets","home-page.next.consumer.sources.visual.source.0.place":"Date","home-page.next.consumer.sources.visual.source.1.title":"Saved places","home-page.next.consumer.sources.visual.source.1.body":"Route + courtyard","home-page.next.consumer.sources.visual.source.1.place":"Place","home-page.next.consumer.sources.visual.source.2.title":"Weekend notes","home-page.next.consumer.sources.visual.source.2.body":"Quiet lunch","home-page.next.consumer.sources.visual.source.2.place":"Preference","home-page.next.consumer.correction.eyebrow":"Corrections that stay","home-page.next.consumer.correction.title.0":"Fix it once","home-page.next.consumer.correction.title.1":"and carry the change forward","home-page.next.consumer.correction.body":"Change a time, remove a wrong assumption, or add a missing preference. Fabric keeps your corrected result, the reason, and the earlier version. This thread or saved routine uses the better choice next time.","home-page.next.consumer.correction.pill.0":"Simple edit","home-page.next.consumer.correction.pill.1":"Reason kept","home-page.next.consumer.correction.pill.2":"History kept","home-page.next.consumer.correction.footer":"The better choice carries forward","home-page.next.consumer.correction.side.title":"Revision record","home-page.next.consumer.correction.side.tag":"CHANGE SAVED","home-page.next.consumer.correction.side.0.label":"Earlier answer","home-page.next.consumer.correction.side.0.value":"Original stays available","home-page.next.consumer.correction.side.1.label":"Change","home-page.next.consumer.correction.side.1.value":"Correction becomes current","home-page.next.consumer.correction.side.2.label":"Reason","home-page.next.consumer.correction.side.2.value":"Explanation stays with edit","home-page.next.consumer.correction.side.3.label":"Next use","home-page.next.consumer.correction.side.3.value":"Better choice carries forward","home-page.next.consumer.correction.side.foot":"Fix once, reuse later","home-page.next.consumer.correction.visual.title":"Revision record","home-page.next.consumer.correction.visual.status":"CORRECTION SAVED","home-page.next.consumer.correction.visual.foot":"Fix once, reuse later","home-page.next.consumer.correction.visual.before.label":"Earlier version","home-page.next.consumer.correction.visual.before.body":"Lunch at 12:00 beside the harbour","home-page.next.consumer.correction.visual.before.note":"Original","home-page.next.consumer.correction.visual.after.label":"Current version","home-page.next.consumer.correction.visual.after.body":"Lunch at 13:00 after a longer museum visit","home-page.next.consumer.correction.visual.after.note":"Corrected","home-page.next.consumer.correction.visual.saved.title":"Correction saved","home-page.next.consumer.correction.visual.saved.body":"Reason + history kept","home-page.next.consumer.routine.eyebrow":"Make repeat work lighter","home-page.next.consumer.routine.title.0":"Save what worked","home-page.next.consumer.routine.title.1":"and review it next time","home-page.next.consumer.routine.body":"Save the steps behind a weekly plan, recurring comparison, or regular update. Fabric gathers the new material, prepares the same first pass, and stops for your review. Change any step or pause the routine whenever it no longer fits.","home-page.next.consumer.routine.pill.0":"Saved steps","home-page.next.consumer.routine.pill.1":"Your review","home-page.next.consumer.routine.pill.2":"Pause anytime","home-page.next.consumer.routine.footer":"Repeat the steps, keep the final choice","home-page.next.consumer.routine.side.title":"Saved routine","home-page.next.consumer.routine.side.tag":"REVIEW REQUIRED","home-page.next.consumer.routine.side.0.label":"Collect","home-page.next.consumer.routine.side.0.value":"Bring in the latest material","home-page.next.consumer.routine.side.1.label":"Prepare","home-page.next.consumer.routine.side.1.value":"Create the same first pass","home-page.next.consumer.routine.side.2.label":"Review","home-page.next.consumer.routine.side.2.value":"You make the final call","home-page.next.consumer.routine.side.3.label":"Change","home-page.next.consumer.routine.side.3.value":"Edit or pause any time","home-page.next.consumer.routine.side.foot":"Nothing finishes without you","home-page.next.consumer.routine.visual.title":"Saved routine","home-page.next.consumer.routine.visual.status":"READY TO REUSE","home-page.next.consumer.routine.visual.foot":"Nothing finishes without you","home-page.next.consumer.routine.visual.day.0.label":"Mon","home-page.next.consumer.routine.visual.day.0.title":"New notes","home-page.next.consumer.routine.visual.day.0.body":"Added to folder","home-page.next.consumer.routine.visual.day.1.label":"Tue","home-page.next.consumer.routine.visual.day.1.title":"Context check","home-page.next.consumer.routine.visual.day.1.body":"Gaps marked","home-page.next.consumer.routine.visual.day.2.label":"Wed","home-page.next.consumer.routine.visual.day.2.title":"First pass","home-page.next.consumer.routine.visual.day.2.body":"Sources attached","home-page.next.consumer.routine.visual.day.3.label":"Thu","home-page.next.consumer.routine.visual.day.3.title":"Your check","home-page.next.consumer.routine.visual.day.3.body":"You decide","home-page.next.consumer.routine.visual.day.4.label":"Next","home-page.next.consumer.routine.visual.day.4.title":"Ready","home-page.next.consumer.routine.visual.day.4.body":"Waits for next use","home-page.next.consumer.routine.visual.recipe.title":"Weekly plan","home-page.next.consumer.routine.visual.recipe.body":"Collect, prepare, review","home-page.next.consumer.routine.visual.recipe.state":"Review on","home-page.next.consumer.sharing.eyebrow":"Share only what matters","home-page.next.consumer.sharing.title.0":"Share the result","home-page.next.consumer.sharing.title.1":"without sharing your workspace","home-page.next.consumer.sharing.body":"Invite someone to a plan, answer, or routine and choose whether they can view, comment, or edit. Your private notes, unrelated folders, and other conversations stay out of sight. Change or remove access later.","home-page.next.consumer.sharing.pill.0":"One item","home-page.next.consumer.sharing.pill.1":"View, comment, edit","home-page.next.consumer.sharing.pill.2":"Change anytime","home-page.next.consumer.sharing.footer":"Only the selected result is shared","home-page.next.consumer.sharing.side.title":"Share settings","home-page.next.consumer.sharing.side.tag":"ONE RESULT","home-page.next.consumer.sharing.side.0.label":"You","home-page.next.consumer.sharing.side.0.value":"Keep full control","home-page.next.consumer.sharing.side.1.label":"Can edit","home-page.next.consumer.sharing.side.1.value":"May change the result","home-page.next.consumer.sharing.side.2.label":"Can comment","home-page.next.consumer.sharing.side.2.value":"May leave feedback","home-page.next.consumer.sharing.side.3.label":"Everyone else","home-page.next.consumer.sharing.side.3.value":"No access","home-page.next.consumer.sharing.side.foot":"Only this result is shared","home-page.next.consumer.sharing.visual.title":"Share settings","home-page.next.consumer.sharing.visual.status":"ONE ITEM SELECTED","home-page.next.consumer.sharing.visual.foot":"Only this result is shared","home-page.next.consumer.sharing.visual.item.title":"Weekend plan","home-page.next.consumer.sharing.visual.item.body":"This result only","home-page.next.consumer.sharing.visual.person.0.initial":"YOU","home-page.next.consumer.sharing.visual.person.0.name":"You","home-page.next.consumer.sharing.visual.person.0.access":"Owner","home-page.next.consumer.sharing.visual.person.1.initial":"SA","home-page.next.consumer.sharing.visual.person.1.name":"Sam","home-page.next.consumer.sharing.visual.person.1.access":"View + comment","home-page.next.consumer.sharing.visual.person.2.initial":"MI","home-page.next.consumer.sharing.visual.person.2.name":"Mila","home-page.next.consumer.sharing.visual.person.2.access":"No access","home-page.next.consumer.sharing.visual.person.3.initial":"OTH","home-page.next.consumer.sharing.visual.person.3.name":"Everyone else","home-page.next.consumer.sharing.visual.person.3.access":"No access","home-page.next.consumer.sharing.visual.rule.label":"Share rule","home-page.next.consumer.sharing.visual.rule.value":"Only this result","home-page.next.consumer.underneath.eyebrow":"One familiar place","home-page.next.consumer.underneath.title.0":"Stay in one workspace","home-page.next.consumer.underneath.title.1":"as the task changes","home-page.next.consumer.underneath.body":"You work entirely in Fabric. Read files, ask follow-up questions, check sources, save a correction, and reuse a routine without moving the task between apps. Your folders and threads stay familiar from the first question to the finished result.","home-page.next.consumer.underneath.pill.0":"One workspace","home-page.next.consumer.underneath.pill.1":"No product map","home-page.next.consumer.underneath.pill.2":"Continuous thread","home-page.next.consumer.underneath.footer":"Fabric stays with the task from start to finish","home-page.next.consumer.underneath.side.title":"Your Fabric view","home-page.next.consumer.underneath.side.tag":"ONE WORKSPACE","home-page.next.consumer.underneath.side.0.label":"Start","home-page.next.consumer.underneath.side.0.value":"Question and materials","home-page.next.consumer.underneath.side.1.label":"Work","home-page.next.consumer.underneath.side.1.value":"Answers and follow-ups","home-page.next.consumer.underneath.side.2.label":"Check","home-page.next.consumer.underneath.side.2.value":"Sources and corrections","home-page.next.consumer.underneath.side.3.label":"Keep","home-page.next.consumer.underneath.side.3.value":"Results and routines","home-page.next.consumer.underneath.side.foot":"Everything stays in Fabric","home-page.next.consumer.underneath.visual.title":"Your Fabric view","home-page.next.consumer.underneath.visual.status":"TASK IN ONE PLACE","home-page.next.consumer.underneath.visual.foot":"Everything stays in Fabric","home-page.next.consumer.underneath.visual.surface":"The workspace you use","home-page.next.consumer.underneath.visual.layer.0.title":"Add","home-page.next.consumer.underneath.visual.layer.0.body":"Files and notes","home-page.next.consumer.underneath.visual.layer.1.title":"Ask","home-page.next.consumer.underneath.visual.layer.1.body":"Question and follow-up","home-page.next.consumer.underneath.visual.layer.2.title":"Check","home-page.next.consumer.underneath.visual.layer.2.body":"Sources and changes","home-page.next.consumer.underneath.visual.layer.3.title":"Keep","home-page.next.consumer.underneath.visual.layer.3.body":"Results and routines","home-page.next.consumer.underneath.visual.note":"One Fabric thread from question to result","home-page.next.consumer.exit.eyebrow":"Your work can leave","home-page.next.consumer.exit.title.0":"Take your work","home-page.next.consumer.exit.title.1":"when you are done","home-page.next.consumer.exit.body":"Export your results, sources, saved routines, and change history. Keep the bundle, move it to another tool, or delete the Fabric workspace. The useful context remains readable after you leave.","home-page.next.consumer.exit.pill.0":"Readable export","home-page.next.consumer.exit.pill.1":"Sources included","home-page.next.consumer.exit.pill.2":"Delete workspace","home-page.next.consumer.exit.footer":"Your work stays readable outside Fabric","home-page.next.consumer.exit.side.title":"Workspace export","home-page.next.consumer.exit.side.tag":"READABLE EXPORT","home-page.next.consumer.exit.side.0.label":"Your work","home-page.next.consumer.exit.side.0.value":"Finished answers and plans","home-page.next.consumer.exit.side.1.label":"Your sources","home-page.next.consumer.exit.side.1.value":"Links, passages, originals","home-page.next.consumer.exit.side.2.label":"Your routines","home-page.next.consumer.exit.side.2.value":"Saved steps remain readable","home-page.next.consumer.exit.side.3.label":"Your records","home-page.next.consumer.exit.side.3.value":"Changes keep their history","home-page.next.consumer.exit.side.foot":"Take the useful context","home-page.next.consumer.exit.visual.title":"Workspace export","home-page.next.consumer.exit.visual.status":"READY TO MOVE","home-page.next.consumer.exit.visual.foot":"Take the useful context","home-page.next.consumer.exit.visual.bundle.title":"Weekend plans export","home-page.next.consumer.exit.visual.bundle.body":"Work + sources + routines","home-page.next.consumer.exit.visual.bundle.state":"Ready","home-page.next.consumer.exit.visual.file.0.title":"plans.md","home-page.next.consumer.exit.visual.file.0.body":"Plans + answers","home-page.next.consumer.exit.visual.file.1.title":"sources.json","home-page.next.consumer.exit.visual.file.1.body":"Links + passages","home-page.next.consumer.exit.visual.file.2.title":"originals","home-page.next.consumer.exit.visual.file.2.body":"Files you added","home-page.next.consumer.exit.visual.file.3.title":"routines.json","home-page.next.consumer.exit.visual.file.3.body":"Saved steps","home-page.next.consumer.exit.visual.file.4.title":"history.zip","home-page.next.consumer.exit.visual.file.4.body":"Change history","home-page.next.consumer.exit.visual.action.keep":"Keep in Fabric","home-page.next.consumer.exit.visual.action.move":"Move to another tool","home-page.next.consumer.exit.visual.action.delete":"Delete workspace","home-page.next.technical.foundations.visual.foundation.7.name":"Ledger","home-page.next.technical.foundations.visual.foundation.7.interface":"EventStore / JSONL / SQLite","home-page.next.technical.foundations.visual.foundation.7.invariant":"System events remain append-only and hash-chained","home-page.next.technical.foundations.visual.foundation.8.name":"Knot","home-page.next.technical.foundations.visual.foundation.8.interface":"signed agent events / Merkle root / replay","home-page.next.technical.foundations.visual.foundation.8.invariant":"Agent events fold into one replayable run","home-page.next.technical.foundations.visual.foundation.9.name":"Selvedge","home-page.next.technical.foundations.visual.foundation.9.interface":"sealed transcript / host calls / receipts","home-page.next.technical.foundations.visual.foundation.9.invariant":"Input, code execution, and output stay linked","home-page.next.technical.foundations.visual.foundation.10.name":"HEDL","home-page.next.technical.foundations.visual.foundation.10.interface":"text / binary / MCP adapters","home-page.next.technical.foundations.visual.foundation.10.invariant":"Structure survives compact exchange","home-page.next.technical.foundations.visual.foundation.11.name":"Bindery","home-page.next.technical.foundations.visual.foundation.11.interface":"Rust API / office document formats","home-page.next.technical.foundations.visual.foundation.11.invariant":"Content, not the extension, drives detection","home-page.next.technical.foundations.visual.foundation.12.name":"Winnow","home-page.next.technical.foundations.visual.foundation.12.interface":"providers / typed records / route metadata","home-page.next.technical.foundations.visual.foundation.12.invariant":"The collection route stays attached","home-page.next.technical.foundations.visual.foundation.13.name":"Signum","home-page.next.technical.foundations.visual.foundation.13.interface":"compress / compress_structured / HEDL","home-page.next.technical.foundations.visual.foundation.13.invariant":"Published rules fix the compressed representation","home-page.next.banner.business-composition.eyebrow":"Composition rule","home-page.next.banner.business-composition.title.0":"Use the products the work needs","home-page.next.banner.business-composition.title.1":"and leave the rest outside","home-page.next.banner.business-composition.body":"Eight commercial surfaces do not turn every request into an eight-product route. Fabric keeps the work record coherent while the operating case decides which cognition, knowledge, agent, execution, placement, and accountability boundaries participate. Kera target portfolios remain separately agreed.","home-page.next.banner.business-composition.panel.title":"Route scope","home-page.next.banner.business-composition.panel.tag":"ONLY WHEN NEEDED","home-page.next.banner.business-composition.panel.row.0.label":"Work and authority","home-page.next.banner.business-composition.panel.row.0.value":"Fabric holds the record; Charter keeps rights and responsibilities explicit.","home-page.next.banner.business-composition.panel.row.1.label":"Cognition and knowledge","home-page.next.banner.business-composition.panel.row.1.value":"Loom composes cognition; Spindle governs versioned knowledge.","home-page.next.banner.business-composition.panel.row.2.label":"Agent work","home-page.next.banner.business-composition.panel.row.2.value":"Nexus coordinates multi-agent work; Aura is the software change agent.","home-page.next.banner.business-composition.panel.row.3.label":"Execution and placement","home-page.next.banner.business-composition.panel.row.3.value":"Core executes supported workloads; Mesh places eligible work. Kera is scoped separately.","home-page.next.banner.business-composition.panel.verdict":"The work record is shared. Product participation remains conditional.","home-page.next.banner.business-composition.panel.foot":"One route, explicit boundaries","home-page.next.banner.business-evidence.eyebrow":"Evidence in motion","home-page.next.banner.business-evidence.title.0":"Build the evidence while work moves","home-page.next.banner.business-evidence.title.1":"not after the question arrives","home-page.next.banner.business-evidence.body":"The useful audit trail is the one assembled during the decision. Sources, exceptions, accountable owners, approvals, and returned actions stay attached to the same record, so review begins with evidence rather than reconstruction.","home-page.next.banner.business-evidence.panel.title":"Decision packet","home-page.next.banner.business-evidence.panel.tag":"ASSEMBLED IN BAND","home-page.next.banner.business-evidence.panel.row.0.label":"Source","home-page.next.banner.business-evidence.panel.row.0.value":"The version and relevant passage stay beside the claim.","home-page.next.banner.business-evidence.panel.row.1.label":"Exception","home-page.next.banner.business-evidence.panel.row.1.value":"Open risk stays visible until an owner resolves or accepts it.","home-page.next.banner.business-evidence.panel.row.2.label":"Approval","home-page.next.banner.business-evidence.panel.row.2.value":"The accountable person and approval state remain named.","home-page.next.banner.business-evidence.panel.row.3.label":"Return","home-page.next.banner.business-evidence.panel.row.3.value":"The action and its evidence can be inspected or exported together.","home-page.next.banner.business-evidence.panel.verdict":"Review the record that produced the decision, not a summary written later.","home-page.next.banner.business-evidence.panel.foot":"Evidence grows with the work","home-page.next.banner.technical-foundations.eyebrow":"Substitution rule","home-page.next.banner.technical-foundations.title.0":"A foundation is replaceable only after","home-page.next.banner.technical-foundations.title.1":"its semantics still hold","home-page.next.banner.technical-foundations.body":"The production open catalogue contains fourteen foundations with different responsibilities. A shared language or repository is not the contract. The input shape, interface, invariant, and conformance result are the contract; Jacquard remains adjacent research.","home-page.next.banner.technical-foundations.panel.title":"Boundary test","home-page.next.banner.technical-foundations.panel.tag":"SEMANTICS FIRST","home-page.next.banner.technical-foundations.panel.row.0.label":"Input shape","home-page.next.banner.technical-foundations.panel.row.0.value":"Types, grammar, premises, events, or model state are explicit.","home-page.next.banner.technical-foundations.panel.row.1.label":"Interface","home-page.next.banner.technical-foundations.panel.row.1.value":"The API, ABI, or portable artifact defines the handoff.","home-page.next.banner.technical-foundations.panel.row.2.label":"Invariant","home-page.next.banner.technical-foundations.panel.row.2.value":"A replacement preserves behaviour, ordering, or proof scope.","home-page.next.banner.technical-foundations.panel.row.3.label":"Conformance","home-page.next.banner.technical-foundations.panel.row.3.value":"Pinned cases test substitution at the boundary.","home-page.next.banner.technical-foundations.panel.verdict":"Replace an implementation only after the declared boundary still passes.","home-page.next.banner.technical-foundations.panel.foot":"Fourteen jobs, explicit handoffs","home-page.next.banner.technical-records.eyebrow":"Record boundaries","home-page.next.banner.technical-records.title.0":"Four records answer","home-page.next.banner.technical-records.title.1":"four different questions","home-page.next.banner.technical-records.body":"Reasoning, execution, system provenance, and agent activity are related but not interchangeable. Keeping their scopes separate is what makes an end-to-end trace inspectable without pretending that one receipt proves everything.","home-page.next.banner.technical-records.panel.title":"Record responsibility","home-page.next.banner.technical-records.panel.tag":"NO COLLAPSED CLAIMS","home-page.next.banner.technical-records.panel.row.0.label":"AION","home-page.next.banner.technical-records.panel.row.0.value":"Records reasoning steps and checkable proof against supplied premises.","home-page.next.banner.technical-records.panel.row.1.label":"Selvedge","home-page.next.banner.technical-records.panel.row.1.value":"Records what code ran, from input through sealed host calls to output.","home-page.next.banner.technical-records.panel.row.2.label":"Ledger","home-page.next.banner.technical-records.panel.row.2.value":"Records append-only events across the wider system.","home-page.next.banner.technical-records.panel.row.3.label":"Knot","home-page.next.banner.technical-records.panel.row.3.value":"Records signed agent events and folds them into a replayable run.","home-page.next.banner.technical-records.panel.verdict":"Compose the records for a wider trace. Do not substitute one scope for another.","home-page.next.banner.technical-records.panel.foot":"One layer each, no overlap","home-page.next.close.business.panel.title":"First proof","home-page.next.close.business.panel.tag":"BOUNDED SCOPE","home-page.next.close.business.panel.row.0.label":"Choose real work","home-page.next.close.business.panel.row.0.value":"Use a live workflow with documents, exceptions, and an approval.","home-page.next.close.business.panel.row.1.label":"Name the owner","home-page.next.close.business.panel.row.1.value":"One accountable person owns the baseline and the decision.","home-page.next.close.business.panel.row.2.label":"Compare the result","home-page.next.close.business.panel.row.2.value":"Measure flow, rework, exceptions, evidence effort, and operating cost.","home-page.next.close.business.panel.foot":"Expansion follows evidence","home-page.next.close.technical.panel.title":"Boundary inspection","home-page.next.close.technical.panel.tag":"START WITH DOUBT","home-page.next.close.technical.panel.row.0.label":"Choose the handoff","home-page.next.close.technical.panel.row.0.value":"Start at knowledge, policy, execution, placement, or replay.","home-page.next.close.technical.panel.row.1.label":"Pin the inputs","home-page.next.close.technical.panel.row.1.value":"Fix versions, artifacts, premises, target, and execution mode.","home-page.next.close.technical.panel.row.2.label":"Inspect the return","home-page.next.close.technical.panel.row.2.value":"Judge the boundary by state, trace events, proofs, and receipts.","home-page.next.close.technical.panel.foot":"The returned evidence is the interface","home-page.overview.relationship.foundation":"Open-source foundations","home-page.overview.relationship.systems":"Execution and placement","home-page.overview.relationship.intelligence":"Intelligence and governance","home-page.overview.relationship.outcomes":"Outcome products","home-page.overview.business.aria":"How one accountable operation crosses the Dweve product stack","home-page.overview.business.chrome":"Operating brief","home-page.overview.business.status":"Owner attached","home-page.overview.business.meta":"One operation · four responsibilities","home-page.overview.business.input-label":"The brief","home-page.overview.business.input":"Objective, owner, sources, and policy","home-page.overview.business.thread":"One accountable identity","home-page.overview.business.lane.work":"Work and company","home-page.overview.business.lane.work-detail":"Keep AI work and company records in their proper lifecycle.","home-page.overview.business.lane.judgement":"Knowledge and judgement","home-page.overview.business.lane.judgement-detail":"Ground the work, then produce a traceable result.","home-page.overview.business.lane.action":"Coordination and action","home-page.overview.business.lane.action-detail":"Turn the objective into governed tasks and operator-visible action.","home-page.overview.business.lane.operation":"Compute and placement","home-page.overview.business.lane.operation-detail":"Run the selected work on declared infrastructure.","home-page.overview.business.output-label":"Back to the owner","home-page.overview.business.output":"Result, approvals, evidence, and record","home-page.overview.business.output-detail":"The business receives one reviewable return, not a collection of disconnected system logs.","home-page.overview.business.side-label":"Accountability thread","home-page.overview.business.side-status":"Intact","home-page.overview.business.side.owner":"Named owner","home-page.overview.business.side.owner-detail":"Responsibility stays with the operation from brief to return.","home-page.overview.business.side.boundary":"Visible gates","home-page.overview.business.side.boundary-detail":"Policy and approval remain explicit at every handoff.","home-page.overview.business.side.return":"One record","home-page.overview.business.side.return-detail":"The result rejoins its evidence and decisions before it returns.","home-page.overview.business.side-footer":"Accountability travels with the work","home-page.overview.business.pill.one":"One operation","home-page.overview.business.pill.two":"Eight products","home-page.overview.business.pill.three":"Evidence returned","home-page.overview.technical.aria":"Typed contracts through the Dweve product stack","home-page.overview.technical.chrome":"Contract ladder","home-page.overview.technical.status":"Trace connected","home-page.overview.technical.meta":"Composable · need-led","home-page.overview.technical.request-label":"Caller contract","home-page.overview.technical.stage.interface":"Interface and record","home-page.overview.technical.stage.cognition":"Knowledge and cognition","home-page.overview.technical.stage.coordination":"Coordination and action","home-page.overview.technical.stage.execution":"Runtime and placement","home-page.overview.technical.artifact.record":"work_record","home-page.overview.technical.artifact.trace":"weave_trace","home-page.overview.technical.artifact.plan":"authorised_plan","home-page.overview.technical.artifact.receipt":"execution_receipt","home-page.overview.technical.kera":"A separate graph-native systems product, available when that route is selected.","home-page.overview.technical.selected":"optional path","home-page.overview.technical.return":"Return contract","home-page.overview.technical.side-label":"Caller-visible invariants","home-page.overview.technical.side.identity":"The request ID and pinned inputs follow every derived artifact.","home-page.overview.technical.side.boundary":"Typed handoffs expose policy, execution, and placement decisions.","home-page.overview.technical.side.return":"Output, trace, and receipts rejoin at the caller.","home-page.overview.technical.side-footer":"The route may shorten; the contract does not disappear","home-page.overview.technical.pill.one":"Typed request","home-page.overview.technical.pill.two":"Explicit handoffs","home-page.overview.technical.pill.three":"Traced return","home-page.overview.shared.kera":"Graph-native language and toolchain when selected.","home-page.overview.shared.separate":"Separate product · not a ninth suite surface","home-page.overview.shared.research":"Adjacent research","home-page.overview.shared.research-boundary":"Jacquard, Forge, and Mycelia sit beside the production route. Their presence here does not assert a runtime dependency.","products-overview.opening.business.aria":"Portfolio responsibilities across the Dweve product suite","products-overview.opening.business.chrome":"Portfolio responsibility board","products-overview.opening.business.status":"Boundaries visible","products-overview.opening.business.meta":"8-product suite · 4 responsibility pairs","products-overview.opening.business.col.responsibility":"Responsibility","products-overview.opening.business.col.products":"Products that own it","products-overview.opening.business.col.result":"What the organisation receives","products-overview.opening.business.row.surfaces":"Work and company records","products-overview.opening.business.row.surfaces-result":"AI work and durable company state keep separate owners.","products-overview.opening.business.row.runtimes":"Action and coordination","products-overview.opening.business.row.runtimes-result":"Coding work and multi-agent work keep distinct operating contracts.","products-overview.opening.business.row.cognition":"Knowledge and cognition","products-overview.opening.business.row.cognition-result":"Versioned knowledge and composed reasoning remain inspectable.","products-overview.opening.business.row.execution":"Compute and placement","products-overview.opening.business.row.execution-result":"Execution and infrastructure placement remain separate decisions.","products-overview.opening.business.foot":"Adopt the responsibility you need first; add another when the operating case requires it.","products-overview.opening.business.foot-state":"No forced bundle","products-overview.opening.business.side-title":"Buying boundary","products-overview.opening.business.side-tag":"NEED-LED","products-overview.opening.business.side.first":"Start with the owner","products-overview.opening.business.side.first-detail":"Choose the product responsible for the first operating problem.","products-overview.opening.business.side.expand":"Add a handoff","products-overview.opening.business.side.expand-detail":"Bring in another product when the work crosses a real responsibility boundary.","products-overview.opening.business.side.keep":"Keep the evidence","products-overview.opening.business.side.keep-detail":"Every added boundary must preserve ownership and the review record.","products-overview.opening.business.side-foot":"One suite, explicit commercial scope","products-overview.opening.business.pill.one":"Eight suite products","products-overview.opening.business.pill.two":"Four pairs","products-overview.opening.business.pill.three":"Adopt by need","products-overview.opening.technical.aria":"Typed product contracts in the Dweve suite","products-overview.opening.technical.headline-lead":"One contract per product","products-overview.opening.technical.headline-accent":"in one explicit request path","products-overview.opening.technical.chrome":"Product contract rack","products-overview.opening.technical.status":"Sockets declared","products-overview.opening.technical.meta":"No mandatory end-to-end route","products-overview.opening.technical.rule":"selected product boundary","products-overview.opening.technical.socket.surfaces":"Surface contracts","products-overview.opening.technical.socket.runtimes":"Runtime contracts","products-overview.opening.technical.socket.cognition":"Cognition contracts","products-overview.opening.technical.socket.execution":"Execution contracts","products-overview.opening.technical.kera-contract":"Graph<Ir> -> TargetArtifact","products-overview.opening.technical.foot":"Products compose through declared inputs and outputs.","products-overview.opening.technical.side-title":"Boundary test","products-overview.opening.technical.side-tag":"INSPECT FIRST","products-overview.opening.technical.side.contract":"Read the contract","products-overview.opening.technical.side.contract-detail":"Identify input, output, invariant, and owner.","products-overview.opening.technical.side.state":"Pin the state","products-overview.opening.technical.side.state-detail":"Keep versions and derived artifacts tied to the request.","products-overview.opening.technical.side.failure":"Test failure","products-overview.opening.technical.side.failure-detail":"Check what returns when a selected boundary cannot complete.","products-overview.opening.technical.side-foot":"Composition is explicit, not ambient","products-overview.opening.technical.pill.one":"Typed sockets","products-overview.opening.technical.pill.two":"Replaceable parts","products-overview.opening.technical.pill.three":"Adopt by need","products-overview.opening.shared.kera":"A separate graph-native systems product, selected for its own contract.","products-overview.opening.shared.separate":"Separate product · outside the eight-product suite","products-overview.opening.shared.research":"Adjacent research inventory","products-overview.opening.shared.research-boundary":"Jacquard, Forge, and Mycelia are research tracks beside the portfolio. This board does not claim that the suite depends on them.","open-source-index.opening.business.aria":"The fourteen source-available foundations grouped by accountable architectural job","open-source-index.opening.business.chrome":"Foundation ownership ledger","open-source-index.opening.business.status":"Scopes distinct","open-source-index.opening.business.meta":"14 source-available foundations · 3 research tracks","open-source-index.opening.hero.business.lead":"14 source-available foundations","open-source-index.opening.hero.business.accent":"for AI infrastructure","open-source-index.opening.hero.business.lede":"Dweve's fourteen source-available foundations support self-hosted AI infrastructure: each owns a bounded mechanism and publishes its own terms and evidence. HEDL is public under Apache-2.0; the rest publish in fortnightly rounds from 1 September 2026.","open-source-index.opening.hero.technical.lead":"14 source-available AI foundations","open-source-index.opening.hero.technical.accent":"3 research tracks","open-source-index.opening.hero.technical.lede":"Fourteen source-available foundations expose inspectable contracts. HEDL is a public open-source project under Apache-2.0; the rest publish in fortnightly rounds from 1 September 2026, with terms stated per project. Three research programmes sit beside that route. Follow a handoff, then reproduce the evidence where it matters.","open-source-index.opening.hero.ledger-pill":"14 foundations · 3 research tracks","open-source-index.opening.hero.technical.ledger-value":"14 foundations + 3 research tracks","open-source-index.opening.detail-label":"How to assess a foundation","open-source-index.opening.business.detail-left":"The fourteen foundations each publish a bounded mechanism with its own scope, terms, and evidence, none of it inherited from the set.","open-source-index.opening.business.detail-right":"Group them by architectural job for review, then open the responsible project before assuming a shared runtime dependency.","open-source-index.opening.business.summary.open":"foundations with their own scope","open-source-index.opening.business.summary.jobs":"job families for a first review","open-source-index.opening.business.summary.research":"adjacent research programmes","open-source-index.opening.business.foot":"Review the foundation responsible for the mechanism you need, then verify its own evidence and terms.","open-source-index.opening.business.foot-state":"Ownership located","open-source-index.opening.business.side-title":"Source-status boundary","open-source-index.opening.business.side-tag":"DO NOT COLLAPSE","open-source-index.opening.business.side.open":"Source-available foundation scopes","open-source-index.opening.business.side.open-detail":"Fourteen projects make focused mechanisms available under project-level terms.","open-source-index.opening.business.side.research":"Research programmes","open-source-index.opening.business.side.research-detail":"Jacquard, Forge, and Mycelia remain research, not open-foundation promises.","open-source-index.opening.business.side.owner":"Responsible mechanism","open-source-index.opening.business.side.owner-detail":"Each project owns a bounded job that can be reviewed on its own.","open-source-index.opening.business.side-foot":"Status and responsibility stay separate","open-source-index.opening.technical.aria":"Contract catalogue for the fourteen Dweve foundations","open-source-index.opening.technical.chrome":"Foundation contract catalogue","open-source-index.opening.technical.status":"Interfaces visible","open-source-index.opening.technical.meta":"14 scopes · no universal chain","open-source-index.opening.technical.detail-left":"Read each project as a contract: identify its interface, invariant, and portable boundary before composing it.","open-source-index.opening.technical.detail-right":"The catalogue records verified scope, not an automatic chain; reproduce the evidence under the project's stated conditions.","open-source-index.opening.technical.rule":"Read each scope as a contract, not an automatic dependency","open-source-index.opening.technical.rule-detail":"Projects can compose when selected. This catalogue does not draw an edge without a verified claim.","open-source-index.opening.technical.foot":"Inspect interface, invariant, and evidence at the selected boundary.","open-source-index.opening.technical.side-title":"Contract review","open-source-index.opening.technical.side-tag":"SCOPE FIRST","open-source-index.opening.technical.side.interface":"Interface","open-source-index.opening.technical.side.interface-detail":"Identify the API, ABI, grammar, or portable format.","open-source-index.opening.technical.side.invariant":"Invariant","open-source-index.opening.technical.side.invariant-detail":"State the behaviour another implementation must preserve.","open-source-index.opening.technical.side.evidence":"Evidence","open-source-index.opening.technical.side.evidence-detail":"Verify the claim under the conditions the project actually reports.","open-source-index.opening.technical.side-foot":"A name is not a dependency claim","open-source-index.opening.group.source.title":"Source and structure","open-source-index.opening.group.source.business":"Collection, parsing, documents, and structured meaning.","open-source-index.opening.group.source.technical":"Collection and representation boundaries","open-source-index.opening.group.proof.title":"Rules, proof, and records","open-source-index.opening.group.proof.business":"Policy decisions, checkable proof, events, and signed runs.","open-source-index.opening.group.proof.technical":"Policy, solver, and event contracts","open-source-index.opening.group.simulation.title":"Numerics and simulation","open-source-index.opening.group.simulation.business":"Declared mathematics, simulation exchange, and digital-twin state.","open-source-index.opening.group.simulation.technical":"Numeric, FMI, and event-state contracts","open-source-index.opening.group.exchange.title":"Exchange and boundaries","open-source-index.opening.group.exchange.business":"Compact exchange, sealed execution, and bounded context.","open-source-index.opening.group.exchange.technical":"Serialization, sandbox, and context contracts","open-source-index.opening.shared.research":"Adjacent research inventory","open-source-index.opening.shared.adjacent":"Research · not foundation dependency","open-source-index.opening.shared.research-boundary":"Jacquard, Forge, and Mycelia are shown together because all three belong to the research track. No runtime relationship to the fourteen foundations is asserted here.","open-source-index.opening.research.jacquard":"Web-native, agent-first game engine","open-source-index.opening.research.forge":"Program synthesis research","open-source-index.opening.research.mycelia":"Artificial-life cognition research","open-source-index.opening.contract.collection":"collection","open-source-index.opening.contract.parser-output":"parser output","open-source-index.opening.contract.document-api":"document API","open-source-index.opening.contract.bwks":".bwks","open-source-index.opening.contract.policy-artifact":"policy artifact","open-source-index.opening.contract.smt-proof":"SMT + proof","open-source-index.opening.contract.event-store":"event store","open-source-index.opening.contract.signed-run":"signed run","open-source-index.opening.contract.numeric-profile":"numeric profile","open-source-index.opening.contract.fmi":"FMI 3.0","open-source-index.opening.contract.typed-events":"typed events","open-source-index.opening.contract.text-binary":"text + binary","open-source-index.opening.contract.sealed-receipt":"sealed receipt","open-source-index.opening.contract.compressed-context":"compressed context","page-breadcrumb.c766e66518":"Breadcrumb","pov-consumer-stack.2f775dc426":"One app, eight surfaces, you touch one","pov-consumer-stack.91cafa0f2f":"Curious? Read more","pov-consumer-stack.f3e39480a3":"What this does for you","pov-consumer-stack.0aacec0d08":"under the hood","pov-consumer-stack.ca26d3a843":"runs on","pov-consumer-stack.b900c1e342":"You are here","pov-consumer-stack.051676078d":"You only ever touch the top. Hover the layers below to see what they do for you.","pov-consumer-stack.505519244c":"One app on top. A quiet platform underneath.","pov-consumer-stack.ace2425487":"Your keys","pov-consumer-stack.c88cdae185":"Documented processing boundary","pov-consumer-stack.fb73f10d96":"Your messages are not used to train anything, they do not leave Europe, and you can clear or export them whenever you like.","pov-consumer-stack.0cf5bb8d10":"It stays yours","pov-consumer-stack.d5f412e831":"Kera","pov-consumer-stack.873132a799":"Mesh","pov-consumer-stack.68836c550e":"Core","pov-consumer-stack.9a90abedb1":"The engine and the network keep your answers quick, and keep them on this side of the world, on ordinary machines.","pov-consumer-stack.d2a04407bc":"It runs in Europe","pov-consumer-stack.4a86080d67":"Spindle","pov-consumer-stack.485a04fef4":"Nexus","pov-consumer-stack.af0854de67":"Aura","pov-consumer-stack.0fed3b96cc":"Loom","pov-consumer-stack.37ad940c5f":"A model writes and explains, a coding helper handles anything technical, and small helpers tidy things up inside your app.","pov-consumer-stack.126b8318a2":"It answers","pov-consumer-stack.f849f5469c":"You log in, ask a question, upload a file, or save a small routine. This is the only part you ever need to learn.","pov-consumer-stack.02767f66be":"The one app you open","pov-consumer-stack.a010de5c61":"Fabric","pov-consumer-stack.93f0d27fad":"the brain","pov-consumer-stack.68079a8485":"coding help","pov-consumer-stack.87d61ff74f":"step by step thinking","pov-consumer-stack.05863c7f69":"the memory","pov-consumer-stack.df0cfeb8c3":"the engine","pov-consumer-stack.de41351ce8":"the network","pov-consumer-stack.ff7b8bd73f":"the language underneath","pov-deployment-postures.ca9c3842ab":"Built for the buyer","pov-deployment-postures.56cdcc6292":"Portable workflow contracts across operating models","pov-deployment-postures.d3fad6507f":"Signed artefact for licensed operation","pov-deployment-postures.aa83c19be6":"What procurement asks","pov-deployment-postures.ac879cf437":"no re-platforming","pov-deployment-postures.16367ffb08":"One sealed artefact, three postures","pov-deployment-postures.800648f724":"deployment console","pov-deployment-postures.09433e1ca6":"Proof verified without a network","pov-deployment-postures.3dd6e9240e":"Can we replay it","pov-deployment-postures.9b2ab7faf7":"Signed media, verified offline","pov-deployment-postures.2510f55de2":"How do we update","pov-deployment-postures.d0de86b09b":"Offline, no outbound link","pov-deployment-postures.eddbb3857e":"Where does it run","pov-deployment-postures.ce6eab8f4e":"Fully disconnected. Updates arrive by signed media, proofs verify offline, and there is no outbound dependency at all.","pov-deployment-postures.5df2ebe7c0":"Air-gapped","pov-deployment-postures.5ff67286aa":"Portable artefact you keep running","pov-deployment-postures.c3e028a1a9":"What if we leave","pov-deployment-postures.54541da6d1":"Per-deployment licence","pov-deployment-postures.be1a18cc5d":"How do we pay","pov-deployment-postures.3b85afb4e6":"Your data centre, your keys","pov-deployment-postures.4405690a82":"The licensed platform on your own hardware, in your own data centre, under your own keys. This is where direct product operation and customer-controlled infrastructure begin.","pov-deployment-postures.f6c82c9b8c":"Licensed","pov-deployment-postures.35e8af01e4":"Trace attaches to every answer","pov-deployment-postures.5f69a557e5":"Flat-rate, no per-token surprises","pov-deployment-postures.2ceb1f43b0":"Fabric on the public Dweve Mesh","pov-deployment-postures.3c9a12626b":"Managed Fabric for teams that want the fastest path to production, with European jurisdiction and a clear operating boundary.","pov-deployment-postures.9b78aaba24":"Business Workspace","pov-deployment-postures.3e58dac50c":"One proof, three operating models","pov-door-chooser.377f415daf":"Use it","pov-door-chooser.cf00482eb4":"A workspace for your teams","pov-door-chooser.9b78aaba24":"Managed Mesh","pov-door-chooser.64579a8be1":"Fabric, ready on day one: chat, documents, workflows, approvals, and evidence in one governed operating surface. The fastest path to value.","pov-door-chooser.10eb415a63":"Best for teams who want results this week, not a build.","pov-door-chooser.a010de5c61":"Fabric","pov-door-chooser.28d9e883f6":"Build on it","pov-door-chooser.af63561d03":"Models and agents through one API","pov-door-chooser.7381649bce":"API access","pov-door-chooser.a1071bbfa0":"Answers with their trace attached, governed agent workflows with owners and control points, and a knowledge layer with provenance on every fact.","pov-door-chooser.ac6aae47ab":"Best for builders embedding AI into their own products.","pov-door-chooser.0fed3b96cc":"Loom","pov-door-chooser.485a04fef4":"Nexus","pov-door-chooser.4a86080d67":"Spindle","pov-door-chooser.af0854de67":"Aura","pov-door-chooser.649c3702f7":"Own it","pov-door-chooser.bc920ddc10":"The whole platform, licensed","pov-door-chooser.08a557101e":"Your hardware","pov-door-chooser.c12506681f":"Run everything on your own hardware, in your own data centre, or fully air-gapped. The same artefact across postures, so there is no re-platforming.","pov-door-chooser.cb511d8238":"Best for regulated estates that must keep the keys.","pov-door-chooser.8cf3c5ea87":"Full stack","pov-door-chooser.ca84f59176":"On-prem","pov-door-chooser.b03d40a138":"Air-gap","pov-door-chooser.68836c550e":"Core","pov-door-chooser.873132a799":"Mesh","pov-door-chooser.d5f412e831":"Kera","pov-door-chooser.68f5a03d78":"Open foundations","pov-door-chooser.54b2257950":"one platform, three doors","pov-door-chooser.0225fdc835":"same engine behind all three","pov-door-chooser.cf9b77061f":"Open","pov-door-chooser.69bd4ef9fb":"View","pov-door-chooser.6fcb21c420":"Behind the","pov-door-chooser.3c55333609":"Open this door","pov-door-chooser.4d5f1d5ba9":"What is inside","pov-door-chooser.725859fd4a":"Every door stands on","pov-door-chooser.898517b369":"Same platform, your choice of door","pov-door-chooser.964253e094":"what you get","pov-door-chooser.95c0247b10":"Chat, documents and workflows in one surface","pov-door-chooser.184476a238":"Live for teams on day one","pov-door-chooser.cc86364684":"No build, no integration project","pov-door-chooser.972e6f48f0":"Models and agents behind one API","pov-door-chooser.12b7a91b2b":"Wire it into what you already run","pov-door-chooser.bef45e6866":"Governance and trace included","pov-door-chooser.b291f87ee6":"The whole stack on your own hardware","pov-door-chooser.e82248b114":"Runs fully air-gapped","pov-door-chooser.0b13859482":"No data leaves your estate","pov-proof-packet.014632ca07":"Source, rule, owner, and replay, attached as the work happens","pov-proof-packet.57168c5b99":"sample steps","pov-proof-packet.6cc1bdc826":"The proof packet","pov-proof-packet.4364c81582":"your residency policy","pov-proof-packet.e7c69d63e0":"the vendor agreement","pov-proof-packet.85752dc814":"Drawn from","pov-proof-packet.7d5a34f718":"No. This processor keeps backups outside the EU, which conflicts with your\n              EU-only residency rule. Onboard only once an EU-region addendum is signed.","pov-proof-packet.c06bb0e434":"Dweve answers","pov-proof-packet.db07117b0d":"Can we onboard this processor under our data-residency policy?","pov-proof-packet.7ace8009b2":"A risk owner asks","pov-proof-packet.ad2d8d4fe6":"Illustrative, until your own data is connected","pov-proof-packet.1eb0d8b618":"Bit-identical, on demand","pov-proof-packet.c0f85d6679":"Replay","pov-proof-packet.aee75cd9e5":"Decisions carry a trace","pov-proof-packet.4e048161ef":"Managed Fabric or a customer-operated licensed estate","pov-proof-packet.c82d1b09cf":"EU","pov-proof-packet.3cdbca630c":"The record is sealed and a replay packet is prepared","pov-proof-packet.888bf5eced":"SEAL","pov-proof-packet.9cd82a6d39":"A named risk owner reviews and signs the decision","pov-proof-packet.501e489055":"OWNER","pov-proof-packet.e40fb76bad":"A conflict is found, so onboarding is blocked for now","pov-proof-packet.02977df2c2":"DECIDE","pov-proof-packet.0b2a8b16ea":"Your EU-only residency rule is in force for this processor","pov-proof-packet.aaa398a28b":"RULE","pov-proof-packet.81b11a63ba":"A backup region outside the EU is found in the agreement","pov-proof-packet.21e5d14e6d":"EXTRACT","pov-proof-packet.bdaa3e45eb":"The vendor agreement and your residency policy are read in","pov-proof-packet.e9ae0ed784":"SOURCE","pov-surface-inspector.68836c550e":"Core","pov-surface-inspector.873132a799":"Mesh","pov-surface-inspector.d5f412e831":"Kera","pov-surface-inspector.68f5a03d78":"Open foundations","pov-surface-inspector.e4428bdd13":"8 surfaces resolved","pov-surface-inspector.4ebd8311c7":"upward depends, never downward","pov-surface-inspector.982c535d9a":"Surface contract","pov-surface-inspector.cf9b77061f":"Open","pov-surface-inspector.88b33bdc3c":"Every surface stands on","pov-surface-inspector.f907c1e0e0":"Eight surfaces, one shared substrate, every contract public","pov-surface-inspector.cf1c85adba":"Position","pov-surface-inspector.d3f0610632":"Outcome","pov-surface-inspector.2c2d93153f":"Depends","pov-surface-inspector.bee831a169":"Substrate","pov-surface-inspector.14dcec2e6c":"upward only","pov-tech-doors.2050522af9":"Take the workspace","pov-tech-doors.605c82c8d3":"Fabric, managed Mesh","pov-tech-doors.084dd970ae":"browser + hosted API","pov-tech-doors.8df1279b32":"org SSO","pov-tech-doors.8d15660985":"operates the platform, owns no layer","pov-tech-doors.a010de5c61":"Fabric","pov-tech-doors.5e3d282743":"Take the API","pov-tech-doors.9281eae80f":"one typed API","pov-tech-doors.332af3bc2d":"REST over TLS","pov-tech-doors.d844975004":"Ed25519-signed","pov-tech-doors.c0f8b03072":"typed, replayable","pov-tech-doors.0fed3b96cc":"Loom","pov-tech-doors.485a04fef4":"Nexus","pov-tech-doors.4a86080d67":"Spindle","pov-tech-doors.af0854de67":"Aura","pov-tech-doors.faa1a73042":"License the stack","pov-tech-doors.07abd646ed":"full stack, your iron","pov-tech-doors.85ad580244":"on-prem or air-gapped","pov-tech-doors.687b476708":"signed bundles","pov-tech-doors.94b50458b7":"customer-held, offline verify","pov-tech-doors.8cf3c5ea87":"Full stack","pov-tech-doors.ca84f59176":"On-prem","pov-tech-doors.b03d40a138":"Air-gap","pov-tech-doors.68836c550e":"Core","pov-tech-doors.873132a799":"Mesh","pov-tech-doors.d5f412e831":"Kera","pov-tech-doors.dda356ac6d":"open foundations","pov-tech-doors.bcd3f7d9a0":"3 paths, one substrate","pov-tech-doors.2c47aa60b2":"contracts public","pov-tech-doors.0c25ce7b56":"Adoption paths","pov-tech-doors.a21834f348":"# Adoption plan, resolved from public contracts","pov-tech-doors.da8bbad2b2":"  # surfaces inside this door","pov-tech-doors.483baae99a":"# same substrate behind all three doors","pov-tech-doors.9e7dee0f44":"Adoption path","pov-tech-doors.ca4be71d9f":"Read the contract","pov-tech-doors.0a6546610c":"Same substrate behind every door, every contract public","pov-tech-doors.404ee2c62c":"3 doors, one graph","pov-why-ai.61bad0c7cf":"It is expensive to run","pov-why-ai.a38e05f388":"Mainstream AI needs GPU clusters just to answer. Procurement turns into a bidding war against the hyperscalers.","pov-why-ai.0dd0f2dd73":"Runs on hardware you already own","pov-why-ai.3c361e253d":"Dweve does its work with binary operations on ordinary processors, so inference costs a fraction of a GPU stack and needs no scarce silicon.","pov-why-ai.9085cc3575":"CPU-native first","pov-why-ai.52f9d78060":"No GPU fleet to procure","pov-why-ai.8fdbe23c0e":"You cannot explain it","pov-why-ai.8ff268d373":"Decisions arrive with no traceable pathway. When a regulator asks how an answer was reached, there is nothing to show.","pov-why-ai.f7c4da802f":"A trace on every answer","pov-why-ai.76e878f02f":"Every answer carries the source it used, the rule it applied, and an owner, so review is structural. You show your work instead of defending a black box.","pov-why-ai.f0d51528e3":"Source and rule attached","pov-why-ai.f19a88aefb":"Replayable on demand","pov-why-ai.9e54754615":"It burns energy","pov-why-ai.b33b409c9a":"Floating-point computation scales badly. The electricity bill compounds, and in a grid-constrained Europe that becomes a hard ceiling.","pov-why-ai.08cf194068":"96% less energy than a GPU stack","pov-why-ai.b4ff05cd24":"Binary constraint operations move far fewer bits per decision. The energy profile does not assume an infinite grid, which is what makes the economics work at scale.","pov-why-ai.a268e26994":"96% less energy","pov-why-ai.03808c4a87":"European by construction","pov-why-ai.7e2b62ef37":"What breaks first","pov-why-ai.ae98e1026c":"Current AI, then the Dweve answer","pov-why-ai.5502a491fa":"3 failure modes, 1 substrate","pov-why-ai.f34d91616d":"The Dweve answer","pov-why-ai.a7200af470":"Three failure modes, one substrate fixes all three","pov-why-ai.fcb037f21f":"Current AI vs Dweve","products-overview.fe0a091fdb":"Products","products-overview.6cc3364a24":"Open source","products-overview.6d3fd427f5":"Inspect proof","products-overview.2c11034cad":"Read the stack","products-overview.791b1c5c8f":"Start with the question you need answered. See what teams use, inspect how the system reaches a result, or read the open foundations underneath it.","products-overview.ff2bf45eaa":"Eight products. Three ways in. One architecture to inspect.","products-overview.f78cdf16d7":"Pick a layer","products-overview.7163afbf4a":"Different posture","products-overview.70e4f2fee8":"Same artefact","products-overview.d5a9f6f81a":"Three postures","products-overview.215475056e":"WHERE IT RUNS","products-overview.1bb5734c67":"Each product owns one job and meets the layer below through a defined boundary. The dependency only runs downward, so a workspace choice never rewrites the foundations beneath it. Open any product page to see where its responsibility starts and stops.","products-overview.8471bf091e":"one shared substrate.","products-overview.5abfb7192d":"Eight commercial surfaces,","products-overview.7a30fa7f40":"The surfaces","products-overview.e6fd6ee7d2":"same substrate behind all three","products-overview.deff33c42b":"licensed: full stack, on your iron","products-overview.3f82565985":"business API and Agent SDK","products-overview.41db7eec6f":"managed Fabric web and app","products-overview.f47e3a13ad":"ADOPTION PATHS","products-overview.3645f7e287":"LICENSED STACK","products-overview.d93d10ff0f":"API","products-overview.703988282e":"WORKSPACE","products-overview.2006795d5b":"There are three practical ways in. Give teams the Fabric workspace, connect products through the API, or license the stack for infrastructure you control. The entry point changes. The product boundaries and underlying architecture do not.","products-overview.43a8b2ccf0":"Three ways in.","products-overview.d2ef2a0bd1":"One platform.","products-overview.123a7f2fcc":"Platform","products-overview.bd97d425c5":"Swap any layer, read the boundary","products-overview.32767bc87c":"Contracts","products-overview.dc5eb704bb":"Public","products-overview.b6ba20c506":"Managed access, licensed, air-gapped","products-overview.2b22237bb7":"Deployment postures","products-overview.09cac2c192":"Workspace, API, licensed stack","products-overview.c6bdade37e":"Ways in","products-overview.9632fe0eff":"One shared substrate","products-overview.138888572a":"Commercial surfaces","products-overview.e0375573b9":"Eight surfaces, three doors, one substrate.","products-overview.9ca5ba27e3":"The platform in short","products-overview.9b950d83a2":"Public, swap any layer","products-overview.94c1bbeea4":"Core, Mesh, Kera, open foundations","products-overview.bee831a169":"Substrate","products-overview.ab3cbb03b3":"Trace attached, replayable","products-overview.af2f32cc92":"Decisions","products-overview.63abb5650f":"Eight","products-overview.aa2a84b29e":"SIGNAL SURFACE","products-overview.3035377d13":"See the doors","products-overview.f5e0b534e7":"Eight products share one architecture without collapsing into one vague suite. Use the workspace, integrate through the API, or license the stack. Each route tells you exactly which products you touch and which responsibilities stay underneath.","products-overview.37219396ca":"One platform. Three ways in. Clear boundaries at every layer.","products-overview.52a8d5d7d8":"See pricing","products-overview.90214883b6":"Talk to us","products-overview.609d9041f2":"Choose the first operating problem. We will help you decide whether it belongs in the workspace, behind an API, or inside a licensed deployment.","products-overview.726ad09bbe":"Use the workspace, build through the API, or run the stack yourself.","products-overview.53410322c6":"Pick your door","products-overview.49f9cde130":"No. Managed Fabric, licensed, and air-gapped deployments use the same underlying platform. You can move from the web app or business API to direct licensed operation without rebuilding your application around a different architecture.","products-overview.8a97921f7b":"Do we have to re-platform to move between tiers?","products-overview.bf794ba2c3":"It runs today, across all eight products, and every figure on this site traces to a source. Ask for a scoped proof of value on one of your own workflows.","products-overview.413d3d0669":"Is this production-ready, or a deck?","products-overview.af8c6a6944":"Keep them. They run on US infrastructure and answer in a chat window. Dweve runs in the EU and attaches the source, owner, and replay to every decision. It is where the regulated work lands.","products-overview.e883ef27a0":"We already pay for Azure OpenAI or Copilot.","products-overview.8b4a3ade13":"No. In managed access, use Fabric through the web app or business API, build through the Agent SDK, and use Nexus and Spindle capabilities through Fabric and the public Mesh. Aura is a separate CLI coding agent. Direct operation of Core, Loom, Nexus, Spindle, Aura, Mesh, Fabric, and Charter belongs to the licensed tiers.","products-overview.768e8125f7":"Do we need all eight products?","products-overview.65cdb1cbfa":"Dweve platform","products-overview.96ce0678f2":"Behind every answer","products-overview.478360978f":"Four guarantees","products-overview.b245297eeb":"Managed, API, and licensed access share one platform architecture. No re-platforming between access models.","products-overview.8bf34da1c7":"One platform","products-overview.3f79b96542":"Binary operations run on the processors you already own. No GPU fleet required.","products-overview.e179db257b":"CPU-native","products-overview.a20f330cb5":"Source, rule, owner, and replay are attached as the work happens.","products-overview.6d4f5ec0dc":"Proof on every decision","products-overview.3daffb419f":"Managed, licensed, or air-gapped. Your data never depends on a US provider.","products-overview.d3dca5bc6d":"EU jurisdiction","products-overview.aa454f4542":"WHAT EVERY ANSWER RESTS ON","products-overview.dfb1d5b6c2":"PORTABILITY","products-overview.e4602b21bb":"READINESS","products-overview.cefb470919":"INCUMBENTS","products-overview.fafd79ebb3":"EIGHT PRODUCTS","products-overview.0e8426df84":"Four questions decide whether the platform is worth a pilot. Here they are, answered plainly.","products-overview.57e5e021db":"not a sales call.","products-overview.2d826a2139":"Straight answers,","products-overview.337ed7bbac":"The questions you are already asking","products-overview.ce234f3a4e":"A sealed packet you can replay","products-overview.305edf1bea":"The owner who signed it off","products-overview.977006dda6":"The rule that decided it","products-overview.d13bfa15ef":"The sources it actually read","products-overview.7bb37db248":"WHAT A DECISION CARRIES","products-overview.931f601dc8":"SEALED","products-overview.501e489055":"OWNER","products-overview.aaa398a28b":"RULE","products-overview.e9ae0ed784":"SOURCE","products-overview.75850f5613":"A trace on every decision means a real question comes back with the source it used, the rule it applied, the owner who signed, and a sealed record you can replay. Here is the shape of that evidence. The example is illustrative until your own data is connected.","products-overview.4358a13d60":"not just the answer.","products-overview.90db876d52":"See the proof,","products-overview.06e09abfa3":"Proof, not just the answer","products-overview.1e41ef2a5f":"No re-platforming","products-overview.7853827da5":"LICENSED","products-overview.67b752639a":"BUSINESS WORKSPACE","products-overview.39fb39c9e1":"Choose managed Fabric access, a licensed deployment on hardware you control, or a fully air-gapped installation with no outbound dependency. The access boundary changes while the platform architecture remains portable, so moving to direct licensed operation does not require a new application architecture.","products-overview.d829b9c34f":"Keep control.","products-overview.560486613b":"Start managed.","products-overview.996bc17e24":"Deployment and jurisdiction","products-overview.79a7e81e7b":"Behind every door","products-overview.1d3c6bc76e":"Same platform","products-overview.72a09cc664":"The whole platform on your hardware, no re-platforming.","products-overview.46fa2dadf3":"Regulated estates license the stack","products-overview.036739e3cc":"Models, agents, and the knowledge pipeline through one API.","products-overview.5e4dc569a6":"Builders take the API","products-overview.85002ce4c2":"Fabric, ready on day one. The fastest path to value.","products-overview.164c82549c":"Teams start with the workspace","products-overview.b977f69816":"Three adoption paths","products-overview.8c8aea63ee":"WHICH DOOR","products-overview.a9bd085d51":"OWN IT","products-overview.1bd37e7996":"BUILD ON IT","products-overview.0487cfb876":"USE IT","products-overview.a3cb71f030":"The decision is not which of eight products to buy. It is how you want to adopt the platform. Start with the workspace your teams use on day one, build on the models and agents through one API, or license the whole stack to run on your own hardware. Each door names what is inside it; the same engine stands behind all three.","products-overview.cf26ab6d15":"All three solved in the substrate","products-overview.4dba36e96c":"Energy bills that compound at scale","products-overview.d1062aa2ae":"Black-box decisions: no trace for the regulator","products-overview.4cb32ee85f":"GPU clusters: expensive and locked to vendors","products-overview.664f3df586":"THE THREE PROBLEMS","products-overview.b3eb6065b2":"ENERGY","products-overview.8c66c9e666":"EXPLAINABILITY","products-overview.39dc45754b":"INFRASTRUCTURE","products-overview.26663a64c6":"current AI.","products-overview.dda004d1d7":"Three things wrong with","products-overview.0550a3ddcb":"Why change","products-overview.03808c4a87":"European by construction","products-overview.5d1cc3c5c6":"Jurisdiction","products-overview.c82d1b09cf":"EU","products-overview.f0dd19bddd":"One coherent architecture","products-overview.ebaccb5304":"Use it, build on it, own it","products-overview.ceac110374":"One architecture, three doors, no re-platforming.","products-overview.1f9bd28c0b":"Most AI tools are expensive to run, impossible to interrogate, and hungry for energy. You need GPU clusters to deploy them, you cannot explain their decisions to a regulator, and the electricity bill compounds at scale. Dweve is built differently: binary constraint operations on the hardware you already own, a decision trace on every answer, and inference that costs a fraction of what a GPU stack would.","products-overview.d85ff911e7":"Trace attached to every answer","products-overview.7ea014de7b":"Evidence","products-overview.0d20e7f51a":"None: same artefact across postures","products-overview.bf5dde2d06":"Lock-in","products-overview.e11ef707f6":"European, by construction","products-overview.4161eb5baf":"Three: managed Mesh, licensed, air-gapped","products-overview.06a29ba476":"Three: use it, build on it, own it","products-overview.857e7030a0":"THE DECISION","products-overview.1d197d39c5":"Where it runs","products-overview.c053262015":"See the three doors","products-overview.d8d05da674":"Dweve is far more than a web interface, especially for companies. Use managed Fabric and its business API on the public Mesh, or license the platform for direct product operation on infrastructure you control. The access and operating rights are explicit at each door.","products-overview.4ba5acce38":"One platform. Three ways in.","products-overview.cf94bdf391":"Ask a question","products-overview.c9a1fcf79b":"Open Fabric","products-overview.a66bd01bad":"No credit card to browse. Most people understand the product in under five minutes.","products-overview.a970a791f7":"Open Fabric. Ask one question. See how it feels.","products-overview.fd00e431ba":"Pick your starting point","products-overview.bed0c4ce4a":"Daily benefit","products-overview.9ef9e640fd":"Quiet engineering","products-overview.045e45ba82":"Your messages stay on this continent.","products-overview.a91bcce893":"Always","products-overview.98e6cf2090":"And you can clear or export that memory.","products-overview.edef810120":"In a chat","products-overview.4b0b86ffad":"Remembers","products-overview.043bd1d190":"Says so instead of inventing something.","products-overview.757b4416f4":"When unsure","products-overview.c9fb22282e":"Refuses","products-overview.2ce2ab3d29":"Shows where it came from, in plain language.","products-overview.8a5949b3f8":"Every answer","products-overview.5361cb5016":"Cites","products-overview.53b29c63ad":"WHY IT FEELS GOOD","products-overview.9e7a17ce95":"YOU TOUCH ONE","products-overview.327b351c17":"EIGHT SURFACES","products-overview.4db4bac423":"ONE PLATFORM","products-overview.fcfbefb3f4":"Fabric is the front door. Loom handles cognition, Nexus organises specialist work, Spindle keeps knowledge connected to its history, Mesh supplies capacity, Aura closes development loops, and Core and Kera run the computation underneath. You do not have to operate those layers to benefit from them. You can inspect each one when the answer matters.","products-overview.5276faf7a1":"You never think about it.","products-overview.1b21e4f258":"A whole platform here.","products-overview.931f137bec":"The rest of it","products-overview.5a1ad01394":"Find the source for this","products-overview.631146c264":"Help me draft a reply","products-overview.9dcbaa5e00":"Explain this step by step","products-overview.abae38727c":"Summarize this PDF","products-overview.87e6386e81":"Answered with sources, in Europe","products-overview.ec59318ed1":"your notes","products-overview.14848a3389":"contract.pdf, page 9","products-overview.637146079e":"The clause changes where your data is stored. Based on the document you shared, it moves storage outside the original region. Here is the exact paragraph it comes from, with a link back so you can check it yourself.","products-overview.77f727a434":"Can you explain why this clause matters, using the file I uploaded?","products-overview.6ed746e25a":"Contract questions","products-overview.8f9db3c3a6":"Saved sources","products-overview.a36b647b97":"Study notes","products-overview.687c82861c":"Documents","products-overview.07c59b4412":"Conversations","products-overview.d60ec603d8":"YOUR WORKSPACE","products-overview.a010de5c61":"Fabric","products-overview.aa773b2ac5":"The agents do the organizing","products-overview.85f7416518":"The compute runs in Europe","products-overview.c7b79ef82e":"The model answers underneath","products-overview.2409167948":"You open Fabric and ask","products-overview.4bef7ee048":"WHAT YOU TOUCH","products-overview.3af629143f":"TRACE INCLUDED","products-overview.dbb15a1dcb":"WORKFLOWS","products-overview.016da0dd9c":"DOCUMENTS","products-overview.26bc51b8c2":"CHAT","products-overview.971681f4ba":"Fabric is the app you actually use. You log in, start a conversation, upload documents, or build a small workflow. Behind the scenes the model powers the answers, the network handles the compute, and the agents do the organizing, but you never have to configure any of that. The trace is always there if you want to see how an answer was reached.","products-overview.e69ddf9cfb":"Everything else is the engine under it.","products-overview.9bb797b2f1":"You open Fabric.","products-overview.68d409a09c":"Your workspace","products-overview.1af2d13404":"See where each answer came from","products-overview.41a1300087":"On every answer","products-overview.2f38169a71":"Trace","products-overview.e75a336e2a":"vs typical AI platforms","products-overview.1ba1c60558":"Energy saved","products-overview.0febbaa4a2":"Your data never leaves Europe","products-overview.8242e0da9d":"Fabric is where you spend your time","products-overview.4ca0a75c2b":"Workspace","products-overview.9436c09954":"You only ever open one thing.","products-overview.fca77b7e3a":"At a glance","products-overview.c006981c0f":"Runs underneath Fabric","products-overview.b31a999e3e":"Everything else","products-overview.eabecefe32":"96% vs typical AI","products-overview.ef55e34494":"Yes, the trace is included","products-overview.00e76b9554":"Can you see how it thinks","products-overview.338d03f42c":"Europe only","products-overview.834cc0e4a2":"Your data stays in","products-overview.91f3964f8e":"The Fabric workspace","products-overview.d2eeb826a4":"Where you start","products-overview.4e6a22430e":"AT A GLANCE","products-overview.04e7217e54":"See what you can do","products-overview.934e6302ec":"You do not need to understand the whole platform. Most people open Fabric, ask a question, and go from there. The model, the compute, and the agents all run beneath it, but you only touch what you actually need.","products-overview.7e6109e3cc":"One place to start. Everything else runs underneath.","products-overview.3a70779dc4":"Fully disconnected. Updates by signed media, proof verified offline, no outbound dependency.","products-overview.5df2ebe7c0":"Air-gapped","products-overview.09776add03":"The platform on your own hardware, in your own data centre, under your own keys.","products-overview.f6c82c9b8c":"Licensed","products-overview.7d39a266ee":"Managed Fabric on the public Mesh. The fastest path to production, within the declared European processing boundary.","products-overview.9b78aaba24":"Managed Mesh","products-overview.cbf52b5350":"What each product carries","products-overview.645367dab1":"Eight products.","products-overview.35c38410bf":"Four jobs your company already has.","products-overview.52ab43b4bf":"Every Dweve product exists because a company function keeps paying for the same gap: work that fragments, knowledge that leaks, records that cannot be shown, and AI spend that grows faster than output. The suite maps onto those jobs directly, so the value case is read per function, not per feature list.","products-overview.277a5e5c06":"OPERATIONS","products-overview.f37b9e1aa4":"FINANCE","products-overview.c4d9bc6083":"COMPLIANCE","products-overview.f9caae1da7":"ENGINEERING","products-overview.1fc05d4d09":"The suite at a glance","products-overview.f30aca5cd4":"eight products, one line each","products-overview.de92ae1ecd":"the exact engine your margins run on","products-overview.f7aab7cae3":"answers that wake only the domain specialists needed","products-overview.cecca49b7b":"reasoning you can put in front of a regulator","products-overview.034d1e55ca":"company knowledge that survives staff turnover","products-overview.3e56d9f718":"shared learning without shared data","products-overview.b2ac7d2a27":"engineering throughput with a full record","products-overview.edd09cbdb4":"one workspace instead of seven subscriptions","products-overview.90d0e3ff50":"the company itself, owned and portable","products-overview.1ad66df972":"one supplier, one boundary","products-overview.4ba8f869b7":"every function covered","products-overview.3d349e1e7d":"The company map","products-overview.77bdafd9f5":"where each product earns its keep","products-overview.1a8a0ba03d":"MAPPED","products-overview.58524ecfdb":"Run the company","products-overview.0079890083":"Charter holds customers, money, work and knowledge on one owned record. Fabric is the workspace your teams actually open.","products-overview.34b6d1bb93":"Control the spend","products-overview.b03c9a7b96":"Core and Loom run on CPUs you already have. The bill scales with use, not with a vendor’s GPU queue.","products-overview.f8f8ecf857":"Answer for decisions","products-overview.a17f6efffd":"Nexus reasons in steps you can show. Spindle keeps every fact with its source, rights and history attached.","products-overview.aa6c92813a":"Build without losing grip","products-overview.6566878323":"Aura closes the engineering loop with human authority intact. Mesh lets sites learn together while data stays home.","products-overview.64b2a1d2a6":"read the case per function, not per feature","products-overview.af3db758af":"every product traces to a cost you already carry","products-overview.3bf48d39aa":"The architecture","products-overview.8e62bd6153":"One stack,","products-overview.0c0108aaec":"from substrate to surface.","products-overview.da803a20f4":"The eight products are not a bundle of acquisitions. They are layers of one system: a numeric substrate, an intelligence layer that activates sparsely, orchestration runtimes that reason and act, and the surfaces people touch. Each layer has a typed contract to the one below it.","products-overview.d7c805806e":"TYPED CONTRACTS","products-overview.f66b3099cb":"ONE SUBSTRATE","products-overview.22fde2a5c8":"CPU-FIRST","products-overview.977a914a65":"Layer to product","products-overview.c483bf2423":"what sits where","products-overview.cda05ca6d8":"Surface","products-overview.d9ba39b784":"Fabric, Aura terminal","products-overview.6926cb0e99":"Orchestration","products-overview.6b55b390ba":"Nexus, Aura, Spindle","products-overview.c698f940a0":"Intelligence","products-overview.e2b95cbc85":"Loom domain-specialist catalogue","products-overview.1d3c457cbe":"Distribution","products-overview.8acf6b6daf":"Mesh, Charter packs","products-overview.a2c675c857":"Core, written in Kera","products-overview.5020167910":"each layer replaceable","products-overview.dbe6570dbd":"contracts stay","products-overview.f40a79f4df":"The layer diagram","products-overview.6ee511d2f5":"products as layers, not tiles","products-overview.12d96aaa33":"STACK","products-overview.0d1086968d":"one dependency direction, downward","products-overview.94f9cb0aad":"Kera is the language underneath, not a product tile","products-overview.1281f1f0fe":"How they compose","products-overview.f9d9a4d072":"Products connect through contracts,","products-overview.58a779b61c":"not through a shared database.","products-overview.aaca96d02c":"Integration is explicit. Fabric talks to runtimes over typed ports. Aura and Nexus draw on Loom through the same routing layer. Spindle feeds verified knowledge to whoever holds the rights. Mesh moves constraint updates, never raw records. You can trace every edge in the diagram to an interface you can read.","products-overview.c25c5c82cf":"TYPED PORTS","products-overview.0c2282a99a":"EXPLICIT EDGES","products-overview.b83144749d":"NO HIDDEN COUPLING","products-overview.6176623f4e":"The edge list","products-overview.42c91ee736":"who talks to whom","products-overview.84e9ce9fd3":"Fabric to runtimes","products-overview.a49ceff9be":"work objects over typed ports","products-overview.9649d893eb":"Runtimes to Loom","products-overview.287f810d20":"domain specialist routing, sparse activation","products-overview.d92fbf12fe":"Spindle to consumers","products-overview.700062800d":"verified atoms, rights attached","products-overview.1b9e066a32":"Mesh between sites","products-overview.e82bd5817f":"constraint updates, never data","products-overview.003e85a2a1":"every edge is an interface","products-overview.1664e21dea":"read it before you rely on it","products-overview.83492059fb":"The composition graph","products-overview.4deba43cfa":"explicit edges between products","products-overview.6dd844704d":"WIRED","products-overview.75fccd030b":"no hidden coupling between products","products-overview.4ef4b33e27":"swap a layer without renegotiating the rest","products-overview.dc19bfddc9":"Behind your workspace","products-overview.91c96e40c7":"You open one app.","products-overview.e7eaf7438e":"A whole team stands behind it.","products-overview.e4673ff48a":"You never have to learn the machinery. You ask in the workspace, and behind the curtain the right parts wake up: a careful brain that only uses what the question needs, helpers that do the legwork, a memory that keeps your facts with their sources, and a home where everything of yours stays yours.","products-overview.f11629b243":"ONE APP","products-overview.6390e7a1e1":"NOTHING TO INSTALL BEHIND IT","products-overview.c34c7b0f24":"YOURS STAYS YOURS","products-overview.1651e53b10":"What stands behind it","products-overview.55cc8b24cb":"in plain words","products-overview.5b981e08b7":"The brain","products-overview.2c9accbaec":"wakes only the parts a question needs","products-overview.b93190b972":"The helpers","products-overview.f2d6aef995":"do the steps and show their work","products-overview.ef2115fcaa":"The memory","products-overview.6a3af6a620":"keeps facts with where they came from","products-overview.cb443a2e2c":"The home","products-overview.55d9ef3db1":"your records stay in one place you own","products-overview.cf79e09f89":"you only meet the workspace","products-overview.7d9171bfbd":"the rest works quietly","products-overview.a13d164d45":"Behind the curtain","products-overview.2fd2ae302a":"what answers when you ask","products-overview.3917a4bff5":"QUIET","products-overview.574980a601":"you never manage the machinery","products-overview.8d2e797f41":"it is all one product family, built to work together","products-overview.3c15ade979":"You drop in a document and ask about it","products-overview.f068050da3":"It reads the file and answers with sources","products-overview.b6cb89c904":"You ask it to sort your notes","products-overview.31b914d8d8":"You build a small workflow","products-overview.60c775e747":"It runs the steps and shows the result","products-overview.d4ba512ff0":"You open the trace on any answer","products-overview.240a59bac5":"You see exactly how it was reached","products-overview.679b8f6603":"Nothing else to set up or install","products-overview.b18861a518":"the answer comes back to you","products-overview.f9c81a6062":"Two ways to run AI","products-overview.adec6a209e":"same workload, two bills","products-overview.30c6561fa1":"COMPARED","products-overview.239f65e0d2":"Mainstream AI","products-overview.a06d84d80b":"rented GPU compute","products-overview.52115b9374":"GPU clusters rented by the hour","products-overview.a264d6724a":"Answers with no traceable path","products-overview.2a2fa6cfdd":"Energy that compounds at scale","products-overview.75270ea5b8":"Locked to one vendor queue","products-overview.1bbe39f6af":"Dweve","products-overview.ce4184029d":"hardware you already own","products-overview.283c40be1b":"Runs on the CPUs you already have","products-overview.e0d70789fa":"A decision trace on every answer","products-overview.65f5efd9b1":"A fraction of the energy","products-overview.1ab15ae203":"One EU supplier, no lock-in","products-overview.cb1141b49c":"same workload","products-overview.179a45dd21":"a fraction of the cost","products-overview.4dc4e1c6a3":"What a decision carries","products-overview.280143c6ec":"four things, attached to the answer","products-overview.96b35db4bc":"ATTACHED","products-overview.6da13addb0":"Source","products-overview.80b5327e77":"the records it actually read","products-overview.78e1790e29":"Rule","products-overview.e6630bcf00":"the policy in force for the decision","products-overview.89ff31225c":"Owner","products-overview.4385b402b7":"the named person who signed it off","products-overview.66c95e7fc7":"Sealed","products-overview.c7ce82d2e7":"a replay packet, bit-identical on demand","products-overview.82cd6601e3":"every answer, fully evidenced","products-overview.a7ce1d31a7":"replayable on demand","products-overview.6de7e52d07":"One place to start.","products-overview.4153c3e654":"Everything else runs underneath.","products-overview.0f05329dd0":"Every layer you can read.","products-overview.88c4f91f10":"The surface contract","products-overview.64f224f930":"what every surface signs up to","products-overview.22b4b0c3c3":"Surfaces","products-overview.4ea33de1b3":"eight, all on one substrate","products-overview.7b4db7ef1f":"Interface","products-overview.85f854bca3":"typed ports, no side channels","products-overview.e6a59b1480":"Swap rule","products-overview.35bb37147d":"any surface replaceable, contracts stay","products-overview.fca5b664f4":"every call readable end to end","products-overview.3961a95070":"one contract beneath all eight","products-overview.33a5062433":"read it in the inspector","products-overview.efbcfeeeeb":"What you never have to do","products-overview.d8bf4ec8e0":"the workspace takes care of it","products-overview.04f87eb3ef":"No installing","products-overview.d7785976ae":"the machinery lives behind the curtain","products-overview.f0f3e329d0":"No choosing engines","products-overview.5cdf587f0f":"the right part wakes up by itself","products-overview.1a03bcb291":"No jargon","products-overview.9bb0ae9056":"you ask in your own words","products-overview.e5a5b8b279":"No worrying where things go","products-overview.0c36bc97fd":"everything stays in your home","products-overview.3ffc205597":"you only meet the front door","products-overview.0e96f6700f":"the rest stays backstage","products-overview.35f8dd422e":"You share a folder and ask across all of it","products-overview.020e9bf6e2":"It only reads what you point it at","products-overview.9b62e05106":"You export a note or a whole thread","products-overview.3078123e74":"Everything leaves with you, nothing is kept back","products-overview.3c29d5a41d":"You come back the next day","products-overview.5623f00132":"Your work is where you left it","products-overview.redo.breadcrumb":"Products","products-overview.opening.relationship.aria":"How foundations support systems, intelligence, governance, and outcome products","products-overview.opening.relationship.foundation":"Open-source foundations","products-overview.opening.relationship.systems":"Execution and placement","products-overview.opening.relationship.intelligence":"Intelligence and governance","products-overview.opening.relationship.outcomes":"Outcome products","products-overview.redo.hero.consumer.eyebrow":"Product guide","products-overview.redo.hero.consumer.lead":"Start with the outcome","products-overview.redo.hero.consumer.accent":"choose your starting point","products-overview.redo.hero.consumer.lede":"Dweve is an AI platform with eight products in its commercial suite and one separate systems product, Kera. You do not need to learn the whole architecture first. Start with the responsibility you want to put in one place, then open the product that owns it.","products-overview.redo.hero.business.eyebrow":"Product portfolio","products-overview.redo.hero.business.lead":"One AI platform","products-overview.redo.hero.business.accent":"three ways in","products-overview.redo.hero.business.lede":"Dweve is an AI platform with managed workspace access and licensed operating paths. It is easier to buy when each boundary stays visible. Eight products form the commercial suite. Kera is a separate systems language and compiler product beneath selected execution paths. The nine detail routes below make that counting rule explicit.","products-overview.redo.hero.technical.eyebrow":"Product contracts","products-overview.redo.hero.technical.lead":"Choose the boundary","products-overview.redo.hero.technical.accent":"trace every contract","products-overview.redo.hero.technical.lede":"Dweve's AI platform separates responsibilities so each handoff stays inspectable. Fabric and Charter own work and company state. Aura and Nexus own action and organisation. Spindle and Loom own knowledge and cognition. Core executes and Mesh places. Kera is the separate graph-native systems language and compiler used by selected deeper paths.","products-overview.redo.hero.action.products":"See the product map","products-overview.redo.hero.action.stack":"Inspect the full stack","products-overview.redo.hero.ledger.label":"Portfolio ledger","products-overview.redo.hero.ledger.pill":"9 routes","products-overview.redo.hero.ledger.suite":"Commercial suite","products-overview.redo.hero.ledger.systems":"Systems product","products-overview.redo.hero.ledger.routes":"Product detail routes","products-overview.redo.hero.ledger.entry":"Entry surfaces","products-overview.redo.section.surfaces.eyebrow":"Work and company","products-overview.redo.section.surfaces.lead":"Two surfaces","products-overview.redo.section.surfaces.accent":"two records","products-overview.redo.section.surfaces.kicker":"The distinction","products-overview.redo.section.runtimes.eyebrow":"Action and organisation","products-overview.redo.section.runtimes.lead":"One bounded action","products-overview.redo.section.runtimes.accent":"is not team coordination","products-overview.redo.section.runtimes.kicker":"The operating boundary","products-overview.redo.section.cognition.eyebrow":"Knowledge and cognition","products-overview.redo.section.cognition.lead":"Govern knowledge","products-overview.redo.section.cognition.accent":"then reason","products-overview.redo.section.cognition.kicker":"The handoff","products-overview.redo.section.execution.eyebrow":"Execution and placement","products-overview.redo.section.execution.lead":"Compute is one decision","products-overview.redo.section.execution.accent":"placement is another","products-overview.redo.section.execution.kicker":"Two contracts","products-overview.redo.section.kera.eyebrow":"The separate systems product","products-overview.redo.section.kera.lead":"The graph is the programme","products-overview.redo.section.kera.accent":"and the targets follow from it","products-overview.redo.section.kera.kicker":"Why it is counted separately","products-overview.redo.pill.work":"Work","products-overview.redo.pill.company":"Company","products-overview.redo.pill.action":"Action","products-overview.redo.pill.organisation":"Organisation","products-overview.redo.pill.knowledge":"Knowledge","products-overview.redo.pill.reasoning":"Reasoning","products-overview.redo.pill.compute":"Compute","products-overview.redo.pill.placement":"Placement","products-overview.redo.pill.graph":"Graph","products-overview.redo.pill.compiler":"Compiler","products-overview.redo.state.workspace":"workspace","products-overview.redo.state.company":"company","products-overview.redo.state.action":"action","products-overview.redo.state.organisation":"organisation","products-overview.redo.state.knowledge":"knowledge","products-overview.redo.state.cognition":"cognition","products-overview.redo.state.compute":"compute","products-overview.redo.state.placement":"placement","products-overview.redo.state.systems":"systems","products-overview.redo.product.fabric.consumer":"The workspace where questions, files, people, helpers and decisions stay attached to the same piece of work.","products-overview.redo.product.fabric.business":"A work-centred AI platform whose durable graph keeps objectives, participants, sources, approvals and outputs independent of the model provider.","products-overview.redo.product.fabric.technical":"A typed work graph for models, agents, knowledge, flows, approvals and composition records across web, API and event surfaces.","products-overview.redo.product.charter.consumer":"One home for customers, money, projects, support, people, documents and the history that joins them.","products-overview.redo.product.charter.business":"A customer-operated company system that keeps parties, money, work, knowledge, policy and events in one operating graph.","products-overview.redo.product.charter.technical":"A typed company graph with policy-bound proposals, deterministic domain invariants, transactional events and replaceable deployment adapters.","products-overview.redo.product.aura.consumer":"An AI coding agent runtime that plans, acts one bounded step at a time, checks the result and can be stopped, corrected or undone.","products-overview.redo.product.aura.business":"An AI coding agent runtime that puts planning, bounded tool actions, outcome checks, human steering, recovery and audit around the model your team chooses.","products-overview.redo.product.aura.technical":"A native control loop with separate planning and execution loops, a fifteen-stage tool pipeline, explicit completion predicates and hash-chained audit.","products-overview.redo.product.nexus.consumer":"A way to give one difficult objective to several specialised helpers while keeping one owner, one answer and one record.","products-overview.redo.product.nexus.business":"A multi-agent runtime for one objective, with agents, tasks, workflows, memory and capability-based routing.","products-overview.redo.product.nexus.technical":"A Python runtime with task lifecycle, workflows, reasoning, five memory systems and capability-based routing.","products-overview.redo.product.spindle.consumer":"Maintains the sources, dates, disagreements and permissions behind an answer, so useful knowledge does not become an untraceable file.","products-overview.redo.product.spindle.business":"Lossless knowledge infrastructure that maintains evidence, rights, policy, lineage, conflict and change as reusable institutional state.","products-overview.redo.product.spindle.technical":"A seven-stage knowledge lifecycle over governed atoms, evidence policies, immutable versions, change propagation and reproducible projections.","products-overview.redo.product.loom.consumer":"Deterministic AI that chooses the right kinds of perception, memory, reasoning and checking for the question instead of treating every task as chat.","products-overview.redo.product.loom.business":"A deterministic AI platform that compiles each task into a typed, neurosymbolic graph of large language models, solvers and verification methods.","products-overview.redo.product.loom.technical":"A cognitive graph compiler spanning perception, four memory purposes, fifteen reasoning forms, a solver fabric and sparse domain specialist routing.","products-overview.redo.product.loom.static.consumer":"Loom builds a task-shaped cognitive path. On supported paths, deterministic execution combines perception, memory, reasoning and checking with domain-specialist help instead of treating every task as chat.","products-overview.redo.product.loom.static.business":"Loom is a task-compiled AI platform. Its governed knowledge state is built through constraint learning and remains distinct from solver methods, while a typed, neurosymbolic graph selects large language models, verification and relevant domain specialists on supported paths with deterministic execution.","products-overview.redo.product.loom.static.technical":"A cognitive graph compiler that keeps constraint learning separate from solving, then routes perception, memory, large language models, reasoning and verification through typed paths with a catalogue of 528 domain specialists.","products-overview.redo.product.core.consumer":"The AI compute stack behind Dweve products, running calculations across ordinary processors and specialised hardware without changing the product above it.","products-overview.redo.product.core.business":"A complete AI compute stack for training and inference that keeps model authoring, optimisation, execution, serving and verification inside one operator system.","products-overview.redo.product.core.technical":"An execution-cell registry covering more than 2,900 operations, 76 categories, 25 format families and twelve backend target families.","products-overview.redo.product.mesh.consumer":"Sovereign AI infrastructure that finds eligible computing capacity while respecting where the work may go, when a machine is available and what evidence must return.","products-overview.redo.product.mesh.business":"Sovereign, distributed AI infrastructure that turns an existing estate into a policy-aware peer-to-peer execution fabric with placement, receipts and local governance.","products-overview.redo.product.mesh.technical":"A self-maintaining peer fabric whose node and workload contracts drive placement, fault handling, protected execution and verifiable receipts.","products-overview.redo.product.kera.consumer":"A graph-native systems language and compiler that keeps a computation's purpose attached while it is planned for different machines, so fewer hidden translation steps own the result.","products-overview.redo.product.kera.business":"A separate graph-native systems language and compiler product that retains types, effects, ownership and execution obligations to target emit.","products-overview.redo.product.kera.technical":"A statically typed systems language, content-addressed .keg graph IR, whole-graph planner, direct code generator and deterministic runtime.","products-overview.redo.consumer.surfaces.body":"Fabric is where a person keeps a piece of work whole. Charter is where an organisation keeps the company whole. They can meet, but neither is a skin over the other.","products-overview.redo.consumer.surfaces.detail":"Choose Fabric when the centre is a question, project, file or decision. Choose Charter when the centre is the customer, payment, employee, subscription or company record that must continue after the conversation ends.","products-overview.redo.consumer.surfaces.footer":"Once the work has a home, the next question is who may act inside it.","products-overview.redo.business.surfaces.body":"Fabric owns governed AI work. Charter owns durable company operation. Combining those responsibilities into one generic platform would make model work and statutory company state share the wrong lifecycle.","products-overview.redo.business.surfaces.detail":"Fabric keeps models, agents, knowledge, flows, approvals and outputs attached to work. Charter keeps parties, money, work, policy and events attached to the company. The boundary makes adoption and accountability legible.","products-overview.redo.business.surfaces.footer":"The surface is only the first boundary. Autonomous work needs its own operating contract.","products-overview.redo.technical.surfaces.body":"Fabric's typed work graph and Charter's typed company graph are distinct domain models. They can exchange recorded operations without collapsing work objects into company records or company invariants into chat state.","products-overview.redo.technical.surfaces.detail":"Fabric carries composition records across model, agent, knowledge and approval nodes. Charter routes reads and signed write proposals through policy, graph and event contracts. Their shared boundary is typed, not implicit glue.","products-overview.redo.technical.surfaces.footer":"Typed surfaces hand work to runtimes that preserve the objective and authority.","products-overview.redo.consumer.runtimes.body":"Aura helps one software task finish safely. Nexus organises several specialised helpers around a wider objective. The difference is the shape of the work, not how many chat windows appear.","products-overview.redo.consumer.runtimes.detail":"Use Aura when the result lives in a codebase and must be tested, steered and recoverable. Use Nexus when work needs roles, handovers, approvals, memory and one record across several kinds of helper.","products-overview.redo.consumer.runtimes.footer":"Helpers still need knowledge they can check and reasoning they can explain.","products-overview.redo.consumer.runtimes.bannerTitle":"One answer can cross several products without becoming one product","products-overview.redo.consumer.runtimes.bannerLead":"Keep each owner","products-overview.redo.consumer.runtimes.bannerAccent":"through the handoff","products-overview.redo.consumer.runtimes.bannerBody":"The workspace, the team of helpers, the reasoning and the calculation keep separate names because each gives you a different kind of control.","products-overview.redo.business.runtimes.body":"Aura owns the engineering action loop. Nexus owns the organisation formed around a goal. Treating both as an agent platform hides the different controls a buyer has to approve.","products-overview.redo.business.runtimes.detail":"Aura checks bounded actions against repository state, tool policy and completion criteria. Nexus governs roles, authority, task ownership, collaboration structures, resource limits, recovery and replay across a team.","products-overview.redo.business.runtimes.footer":"Organisation and action are only defensible when evidence and cognition remain distinct.","products-overview.redo.business.runtimes.bannerTitle":"A product boundary is a responsibility boundary","products-overview.redo.business.runtimes.bannerLead":"Boundaries keep","products-overview.redo.business.runtimes.bannerAccent":"control visible","products-overview.redo.business.runtimes.bannerBody":"Fabric owns work, Nexus owns the organisation, Loom owns cognition and Core owns execution. The handoff is inspectable because no one layer claims the whole result.","products-overview.redo.technical.runtimes.body":"Aura is a native objective-action-observation loop for software work. Nexus is a typed multi-agent runtime with explicit workflow topology, agent lifecycle, authority evaluation and replay.","products-overview.redo.technical.runtimes.detail":"Both can integrate models and tools, but their invariants differ. Aura evaluates real tool outcomes against task criteria. Nexus keeps task state, organisational structure and resource authority independent of any worker or model turn.","products-overview.redo.technical.runtimes.footer":"The runtime can now ask for governed knowledge and a typed cognitive weave.","products-overview.redo.technical.runtimes.bannerTitle":"Composition does not erase ownership","products-overview.redo.technical.runtimes.bannerLead":"Compose the work","products-overview.redo.technical.runtimes.bannerAccent":"retain ownership","products-overview.redo.technical.runtimes.bannerBody":"A typed handoff preserves the work object, organisational decision, cognitive graph and execution record instead of flattening them into one provider trace.","products-overview.redo.consumer.cognition.body":"Spindle keeps information current, sourced and allowed for use. Loom decides how to perceive, remember, reason, solve and explain. One looks after what is known; the other works out what follows.","products-overview.redo.consumer.cognition.detail":"A source can be well supported and still be out of date or not allowed for this use. Spindle carries those facts. Loom receives the permitted knowledge and can explain a disagreement or stop when something essential is missing.","products-overview.redo.consumer.cognition.footer":"A checked conclusion still needs a machine to run it and a place where it is allowed to run.","products-overview.redo.business.cognition.body":"Spindle maintains the governed knowledge asset. Loom compiles a task-specific cognitive graph over the permitted material. This keeps evidence policy separate from reasoning policy.","products-overview.redo.business.cognition.detail":"Spindle preserves source spans, rights, versions, conflicts, quality and change impact before a question is asked. Loom composes learned models, memory, reasoning forms, solvers and verification when the question arrives.","products-overview.redo.business.cognition.footer":"The cognitive contract now passes to execution and placement without changing category.","products-overview.redo.technical.cognition.body":"Spindle emits governed atoms, evidence bundles and reproducible projections. Loom consumes typed knowledge and compiles perception, memory, learned methods, symbolic methods, solvers and verification into one weave.","products-overview.redo.technical.cognition.detail":"The boundary is deliberate. Spindle does not generate language or own workflow authority. Loom does not silently replace evidence policy with a confidence score. Their artefacts retain identity across the handoff.","products-overview.redo.technical.cognition.footer":"The weave identifies what must run. Core and Mesh settle how and where.","products-overview.redo.consumer.execution.body":"Core supplies the calculation. Mesh finds a machine that is capable, available and permitted to do it. A fast machine is not eligible if the work may not cross its boundary.","products-overview.redo.consumer.execution.detail":"Core supports the numerical forms and hardware paths the operation needs. Mesh adds the owner's schedule, location, security rules and required receipt before it places the work.","products-overview.redo.consumer.execution.footer":"Below selected execution paths sits one more product with a different job.","products-overview.redo.consumer.execution.bannerTitle":"Eight in the suite, Kera underneath selected paths","products-overview.redo.consumer.execution.bannerLead":"Count the suite","products-overview.redo.consumer.execution.bannerAccent":"then count routes","products-overview.redo.consumer.execution.bannerBody":"There are nine product detail routes because Kera is a product too. It is counted separately from the eight-product commercial suite so the catalogue does not turn an underlying language into a ninth user-facing surface.","products-overview.redo.business.execution.body":"Core owns the AI execution cell from representation through dispatch and verification. Mesh owns placement across estates, jurisdictions, trust domains and service conditions.","products-overview.redo.business.execution.detail":"Core prevents a backend logo from standing in for real coverage. Mesh prevents raw capacity from standing in for eligible capacity. The two contracts let procurement separate computational reach from operational placement.","products-overview.redo.business.execution.footer":"Kera is neither placement nor the whole suite. It is the separate systems product below selected paths.","products-overview.redo.business.execution.bannerTitle":"The count needs a rule","products-overview.redo.business.execution.bannerLead":"One count cannot","products-overview.redo.business.execution.bannerAccent":"carry two meanings","products-overview.redo.business.execution.bannerBody":"The licensed suite names eight products. Kera has its own product route and contract as a systems language and compiler. Naming both numbers is more useful than forcing one total to carry two meanings.","products-overview.redo.technical.execution.body":"Core resolves an implementation per execution cell from representation, packing, accumulator, shape, policy, backend and determinism contract. Mesh intersects that requirement with the node contract before scheduling.","products-overview.redo.technical.execution.detail":"Core can run natively and, for selected strategic licence paths, on Kera. Mesh may place eligible Core or Kera workloads, but placement remains a workload-node contract rather than part of the compiler or operator registry.","products-overview.redo.technical.execution.footer":"The optional deeper path is Kera, with graph identity retained through emit.","products-overview.redo.technical.execution.bannerTitle":"Route count and suite count describe different sets","products-overview.redo.technical.execution.bannerLead":"Route set differs","products-overview.redo.technical.execution.bannerAccent":"from suite scope","products-overview.redo.technical.execution.bannerBody":"Eight products form the commercial suite. Kera is a separate product with its own route and execution contract. The route set therefore contains nine product detail pages without implying nine peer surfaces.","products-overview.redo.consumer.kera.body":"Kera is the product for teams that need the computation itself to keep its identity while it is planned for CPUs, accelerators, browsers or distributed machines.","products-overview.redo.consumer.kera.detail":"You are unlikely to choose Kera as a workspace. You choose it when the route underneath must keep types, permissions, ownership and machine plans attached to the same computation.","products-overview.redo.consumer.kera.footer":"That completes the nine product routes without pretending all nine are the same kind of product.","products-overview.redo.consumer.kera.closeTitle":"Start with the job","products-overview.redo.consumer.kera.closeAccent":"you need to own","products-overview.redo.consumer.kera.closeBody":"Open a product page for the responsibility you recognise, or inspect the stack when you need to follow the handoffs underneath it.","products-overview.redo.business.kera.body":"Kera is a statically typed systems language, content-addressed graph IR, compiler and runtime. It is a separate commercial product and the optional deeper foundation for selected Core paths.","products-overview.redo.business.kera.detail":"Kera keeps operation meaning, effects, capabilities, ownership, memory spaces and execution obligations available to planning and direct target emission. It is not open source and it is not a ninth peer surface in the licensed suite.","products-overview.redo.business.kera.footer":"The portfolio is now classified by responsibility, commercial set and route set.","products-overview.redo.business.kera.closeTitle":"Choose a boundary","products-overview.redo.business.kera.closeAccent":"you can hold accountable","products-overview.redo.business.kera.closeBody":"Use the product map to scope the responsibility, the stack page to inspect handoffs and the pricing route to choose an operating posture.","products-overview.redo.technical.kera.body":"Kera treats a typed, effect-tracked, content-addressed graph as the durable programme. Whole-graph planning, direct code generation and runtime execution derive from that one identity.","products-overview.redo.technical.kera.detail":"Core Native does not require Kera. Core on Kera is an optional selected path that adds graph-native planning and pure deterministic support for covered floating-family execution. That direction matters: Core can use Kera, not the reverse.","products-overview.redo.technical.kera.footer":"Every product route now names its own contract and the exact boundary below it.","products-overview.redo.technical.kera.closeTitle":"Follow the contract","products-overview.redo.technical.kera.closeAccent":"then inspect the implementation","products-overview.redo.technical.kera.closeBody":"The stack page separates responsibility handoffs from real dependencies and links each product to the foundations it can actually claim.","products-overview.redo.side.surfaces.label":"Entry surfaces","products-overview.redo.side.surfaces.sub":"two durable centres","products-overview.redo.side.surfaces.tag":"entry","products-overview.redo.side.runtimes.label":"Runtime choice","products-overview.redo.side.runtimes.sub":"one task or one team","products-overview.redo.side.runtimes.tag":"control","products-overview.redo.side.runtimes.foot":"two invariants","products-overview.redo.side.cognition.label":"Knowledge handoff","products-overview.redo.side.cognition.sub":"evidence then method","products-overview.redo.side.cognition.tag":"typed","products-overview.redo.side.cognition.foot":"state then weave","products-overview.redo.side.execution.label":"Execution contract","products-overview.redo.side.execution.sub":"capability plus eligibility","products-overview.redo.side.execution.tag":"placed","products-overview.redo.side.execution.foot":"run then place","products-overview.redo.side.kera.label":"Product class","products-overview.redo.side.kera.sub":"language and compiler","products-overview.redo.side.kera.tag":"separate","products-overview.redo.side.kera.foot":"product P09","products-overview.redo.side.owner":"owner","products-overview.redo.side.boundary":"boundary","products-overview.redo.side.contract":"contract","products-overview.redo.side.classification":"classification","products-overview.redo.frame.surfaces.title":"portfolio / entry-surfaces","products-overview.redo.frame.surfaces.verdict":"Two entry surfaces, no false parent-child relationship","products-overview.redo.frame.runtimes.title":"portfolio / action-runtimes","products-overview.redo.frame.runtimes.verdict":"Aura owns the loop. Nexus owns the organisation.","products-overview.redo.frame.cognition.title":"portfolio / knowledge-cognition","products-overview.redo.frame.cognition.verdict":"Spindle maintains evidence. Loom composes cognition.","products-overview.redo.frame.execution.title":"portfolio / execution-envelope","products-overview.redo.frame.execution.verdict":"Core establishes capability. Mesh establishes eligible placement.","products-overview.redo.frame.kera.title":"portfolio / kera-path","products-overview.redo.frame.kera.verdict":"The graph remains the programme through planning and target emit.","products-overview.redo.frame.kera.graph":"Content-addressed graph","products-overview.redo.frame.kera.graph.body":"Typed ports, effects, ownership, memory spaces and dependencies remain attached in the .keg artefact.","products-overview.redo.frame.kera.targets":"Target plans","products-overview.redo.frame.kera.targets.body":"Supported CPU, accelerator, WebAssembly and distributed targets receive plans from the same graph identity.","products-overview.redo.frame.kera.targets.state":"targeted","products-overview.redo.frame.status.separate":"separate","products-overview.redo.frame.status.routed":"routed","products-overview.redo.frame.status.typed":"typed","products-overview.redo.frame.status.placed":"placed","products-overview.redo.frame.status.compiled":"compiled","products-overview.redo.frame.meta.twoProducts":"2 products","products-overview.redo.frame.meta.twoRuntimes":"2 runtimes","products-overview.redo.frame.meta.twoResponsibilities":"2 responsibilities","products-overview.redo.frame.meta.computeEnvelope":"compute / placement","products-overview.redo.frame.meta.separateProduct":"route P09","products-overview.redo.banner.one.eyebrow":"Responsibility chain","products-overview.redo.banner.one.instrument":"Responsibility handoff","products-overview.redo.banner.one.verdict.label":"Owned boundary","products-overview.redo.banner.two.eyebrow":"Counting rule","products-overview.redo.banner.two.instrument":"Portfolio census","products-overview.redo.banner.two.verdict.label":"Verified count","products-overview.redo.banner.two.verdict.value":"Eight suite products and one separate systems product make nine product routes.","products-overview.redo.banner.suite.name":"Commercial suite","products-overview.redo.banner.suite.body":"Core, Loom, Nexus, Spindle, Aura, Mesh, Fabric and Charter.","products-overview.redo.banner.suite.state":"8 products","products-overview.redo.banner.kera.body":"A separate systems language and compiler product beneath selected execution paths.","products-overview.redo.banner.kera.state":"separate","products-overview.redo.banner.routes.name":"Product routes","products-overview.redo.banner.routes.body":"Eight suite detail pages plus the separate Kera detail page.","products-overview.redo.banner.routes.state":"9 routes","products-overview.redo.close.eyebrow":"Next step","products-overview.redo.close.stack":"Inspect the stack","products-overview.redo.close.pricing":"See pricing","products-overview.redo.close.contact":"Scope a deployment","products-overview.redo.close.panel.title":"What the catalogue holds","products-overview.redo.close.panel.tag":"9 routes","products-overview.redo.close.panel.row.0.label":"Commercial suite","products-overview.redo.close.panel.row.0.value":"Eight products across four responsibility pairs","products-overview.redo.close.panel.row.1.label":"Systems product","products-overview.redo.close.panel.row.1.value":"Kera, separate from the suite and selected per route","products-overview.redo.close.panel.row.2.label":"Entry surfaces","products-overview.redo.close.panel.row.2.value":"Fabric for the work, Charter for the company","products-overview.redo.close.panel.foot":"Every product route names its own contract.","products-overview.redo.side.surfaces.foot":"Two entry surfaces, one route each","products-overview.redo.frame.meta.twoSurfaces":"2 surfaces","qa-block.002ff59811":"Question","qa-block.a16a4eda7c":"Answer","suite-business-glyph.377f415daf":"Use it","suite-business-glyph.94d17188e9":"The workspace, ready day one","suite-business-glyph.28d9e883f6":"Build on it","suite-business-glyph.60f6268804":"One API to models and agents","suite-business-glyph.649c3702f7":"Own it","suite-business-glyph.481fde3e49":"The whole stack on your hardware","suite-business-glyph.9a973e0e4a":"GPU clusters to deploy","suite-business-glyph.77753d7d6c":"CPU native, hardware you own","suite-business-glyph.19adfc34cc":"Black-box decisions","suite-business-glyph.7d088e8949":"Proof on every answer","suite-business-glyph.fb5509646c":"Energy bills that compound","suite-business-glyph.a268e26994":"96% less energy","suite-business-glyph.3fe1b92845":"Re-platform to scale","suite-business-glyph.888e0b90ad":"Same artefact, every posture","suite-business-glyph.9b78aaba24":"Managed Mesh","suite-business-glyph.f6c82c9b8c":"Licensed","suite-business-glyph.5df2ebe7c0":"Air-gapped","suite-business-glyph.55acf508d8":"The decision","suite-business-glyph.8bf34da1c7":"One platform","suite-business-glyph.54acc2806d":"Start here","suite-business-glyph.b7a3f27883":"Risk removed","suite-business-glyph.f77e84bdfd":"typical AI, then Dweve","suite-business-glyph.e11ef707f6":"European, by construction","suite-consumer-glyph.ccfe691658":"Everything else runs underneath","suite-consumer-glyph.a010de5c61":"Fabric","suite-consumer-glyph.23a058d15f":"Open here","suite-consumer-glyph.d2eeb826a4":"Where you start","suite-consumer-glyph.32528b2aa2":"The part that keeps it safe","suite-consumer-glyph.b1c6fa0b03":"The part that does the work","suite-consumer-glyph.5e2993477e":"The part that answers","suite-consumer-glyph.d0173a08de":"Boundary stated in the terms","suite-consumer-glyph.ce16cfa9c1":"Answers you can check","suite-consumer-glyph.3dd34c4d05":"You only open one thing","suite-hero-glyph.ddd0681012":"Air","suite-hero-glyph.f6c82c9b8c":"Licensed","suite-hero-glyph.c82d1b09cf":"EU","suite-hero-glyph.87d635c3e6":"Business Workspace","suite-hero-glyph.e179db257b":"CPU-native","suite-hero-glyph.a268e26994":"96% less energy","suite-hero-glyph.4db4bac423":"ONE PLATFORM","suite-hero-glyph.653a698b88":"proof attached","suite-hero-glyph.bfc529fc74":"Execution path","suite-hero-glyph.aa052c01a9":"Seven surfaces","suite-hero-glyph.1145690c5c":"one request, traced","suite-hero-glyph.8c32819744":"Stack map","suite-hero-glyph.65c821a596":"Live","suite-hero-glyph.28733328c3":"7 surfaces, 1 substrate, EU","suite-hero-glyph.a68b38a624":"Dweve Platform","suite-hero-glyph.7b9dec8ec8":"Mesh, runs in EU jurisdiction","suite-hero-glyph.1d61ed55be":"Core, binary path, CPU native","suite-hero-glyph.27df560ee6":"Loom, domain specialist route selected","suite-hero-glyph.12689da26a":"Spindle, sources and provenance","suite-hero-glyph.896af91315":"Nexus, policy and audit","suite-hero-glyph.14b7337c8b":"request, Fabric workspace","suite-hero-glyph.a010de5c61":"Fabric","suite-hero-glyph.af0854de67":"Aura","suite-hero-glyph.873132a799":"Mesh","suite-hero-glyph.4a86080d67":"Spindle","suite-hero-glyph.485a04fef4":"Nexus","suite-hero-glyph.0fed3b96cc":"Loom","suite-hero-glyph.68836c550e":"Core","suite-hero-glyph.d5f412e831":"Kera","workspace-mockup.2eb56be3c2":"Sources","workspace-mockup.a010de5c61":"Fabric","workspace-mockup.905cb326c7":"You","workspace-mockup.fffbce7dc4":"Ask anything","workspace-mockup.f9312169ef":"Pinned","workspace-mockup.19adc47be3":"Folders"}