Add warranted agent specs and positioning

Author: FlowmemoryAI

README.md

@@ -266,12 +266,15 @@ Start here for review:
 - `docs/ARCHITECTURE_DIAGRAMS.md`
 - `docs/THREAT_MODEL.md`
 - `docs/CLAIM_BOUNDARIES.md`
+- `docs/MARKETING_POSITIONING.md`
 - `docs/AGENT_RUNTIME.md`
 - `docs/RUNTIME_STATE_MACHINE.md`
 - `docs/AGENT_REGISTRY.md`
 - `docs/EVIDENCE_SCHEMA.md`
 - `docs/LAUNCH_CHECKLIST.md`
 - `specs/WarrantedAgentFramework.v0.md`
+- `specs/RuntimeStateMachine.v0.md`
+- `specs/EvidenceSchemas.v0.md`
 - `examples/warranted_agents/README.md`
 
 ## Non-Claims

docs/MARKETING_POSITIONING.md

@@ -0,0 +1,76 @@
+# Marketing Positioning
+
+## Core Line
+
+```text
+Generic agents make claims. FlowMemory agents can leave warranted receipts.
+```
+
+## Category Line
+
+```text
+Available is not enough. Warrantable is the standard.
+```
+
+## Simple Explanation
+
+Most AI agents can act, call tools, and move through workflows.
+
+FlowMemory asks the harder question:
+
+```text
+What happens when the agent makes a promise?
+```
+
+FlowMemory Warranted Agents turns that promise into:
+
+- a PolicyCard;
+- a bond-modeled warranty;
+- required evidence envelopes;
+- a deterministic runtime history;
+- a FlowPulse-style memory artifact;
+- a private scoped proof the user can carry.
+
+## 60-Second Script
+
+```text
+AI agents are becoming workers.
+
+They can research, code, transact, and act across the internet.
+
+But most agents still ask users for trust.
+
+FlowMemory changes the standard.
+
+Generic agents make claims.
+FlowMemory agents can leave warranted receipts.
+
+The user defines the promise in a PolicyCard.
+The agent quotes the work and puts a bond behind it.
+The runtime records the machine history.
+The evidence schema checks the receipt path.
+FlowBond settles the outcome.
+PulsePass gives the user scoped private proof.
+
+If the agent closes the obligation, the warranty releases.
+If payment happens without the required delivery path, the local model pays the user from the bond.
+
+This is not just another agent log.
+It is the start of warranted agent infrastructure.
+
+Available is not enough.
+Warrantable is the standard.
+```
+
+## Short Lines
+
+- Agents with money on the line.
+- Promises should have receipts.
+- The user owns the rule. The agent bonds the promise.
+- Agent work should be warrantable, not just available.
+- FlowMemory turns agent promises into machine histories.
+- A valid action surface is not always a valid machine history.
+
+## Boundary
+
+This language is for the local v0 architecture. It does not claim custody, wallet enforcement, production settlement, production adjudication, full privacy, zero-knowledge privacy, semantic truth, work-quality proof, or production verifier infrastructure.

specs/EvidenceSchemas.v0.md

@@ -0,0 +1,61 @@
+# Evidence Schemas v0
+
+## Purpose
+
+Define the local evidence envelope shapes used by FlowMemory Warranted Agents.
+
+Evidence names are not enough. Each envelope type carries required fields.
+
+## Envelopes
+
+### `PaymentReceiptEnvelope`
+
+Purpose:
+
+```text
+Proves a payment-like obligation event was observed by the local model.
+```
+
+Required fields:
+
+- `receiptStatus`: string, must equal `settled`.
+
+### `WorkDeliveryEnvelope`
+
+Purpose:
+
+```text
+Binds the claimed work delivery to a content commitment.
+```
+
+Required fields:
+
+- `artifactHash`: string, must begin with `sha256:`.
+
+### `AcceptanceEnvelope`
+
+Purpose:
+
+```text
+Records that the user-side acceptance condition closed.
+```
+
+Required fields:
+
+- `accepted`: boolean, must equal `true`.
+
+### `FlowPulseReceiptEnvelope`
+
+Purpose:
+
+```text
+Binds the action to a FlowPulse-style memory receipt.
+```
+
+Required fields:
+
+- `pulseObserved`: boolean, must equal `true`.
+
+## Boundary
+
+These schemas are local field checks. They do not claim semantic truth, work-quality proof, external verification, production private compute, or production verifier infrastructure.

specs/RuntimeStateMachine.v0.md

@@ -0,0 +1,59 @@
+# Runtime State Machine v0
+
+## Purpose
+
+Define the local deterministic state contract for a FlowMemory warranted-agent action.
+
+## States
+
+- `INITIAL`
+- `MANIFEST_LOADED`
+- `POLICY_QUOTED`
+- `BOND_LOCKED`
+- `ACTION_EXECUTED`
+- `FLOWBOND_SETTLED`
+- `PRIVATE_PROOF_READY`
+- `WARRANTY_RELEASED`
+- `USER_PAID_FROM_BOND`
+
+## Terminal States
+
+- `WARRANTY_RELEASED`
+- `USER_PAID_FROM_BOND`
+
+## Allowed Transitions
+
+| From | To |
+| --- | --- |
+| `INITIAL` | `MANIFEST_LOADED` |
+| `MANIFEST_LOADED` | `POLICY_QUOTED` |
+| `POLICY_QUOTED` | `BOND_LOCKED` |
+| `BOND_LOCKED` | `ACTION_EXECUTED` |
+| `ACTION_EXECUTED` | `FLOWBOND_SETTLED` |
+| `FLOWBOND_SETTLED` | `PRIVATE_PROOF_READY` |
+| `PRIVATE_PROOF_READY` | `WARRANTY_RELEASED` |
+| `PRIVATE_PROOF_READY` | `USER_PAID_FROM_BOND` |
+
+## Transition Fields
+
+Each transition includes:
+
+- `fromState`
+- `toState`
+- `phase`
+- `status`
+- `idempotencyKey`
+- `fields`
+- `transitionHash`
+
+## Rejection Rules
+
+The local state machine rejects:
+
+- transitions not listed above;
+- duplicate idempotency keys;
+- transitions after a terminal state.
+
+## Boundary
+
+This spec does not define wallet execution, custody, distributed consensus, production settlement, or production verifier infrastructure.