Product explorer / public teaching examples
Explore State through connected examples
Discover History, operational memory, context zoom, dependencies, access, efficiency, and recovery through a software-release or NFL-shaped scenario.
Find a familiar problem, change a fixture, and inspect the exact consequence and its limits.
In short
Try a public example and inspect it through seven connected views. Compare a correction, find stale work, focus the selected context, or examine a denied read. The examples are teaching simulations, not live engine results.
Available today: An interactive website feature with authored public fixtures. No backend, AWS, or model execution.
Browse by problem or capability#
Choose a problem such as lost context, stale results, repeated work, or denied access. All seven views share the same selected scenario, event, record, and version. You can explore freely or follow the optional three-stop guide.
Three statuses that must not be confused#
Capability availability
Whether the underlying product capability is implemented in source, local only, or planned. A working website interaction does not make a planned managed service available.
Demonstration mode
Public synthetic fixtures. No engine, AWS, agent, or model is running on this page.
Scenario result
Accepted, stale, pending, expired, and denied are states inside a public fixture. They are not live production results.
Git-like History#
Compare exact versions without overwriting the earlier record.
Exact revisions + generation-pinned membership
Exact History is implemented in source, not hosted here. Git-like describes version history, not Git compatibility, branching, or undoing external actions.
Operational Memory#
Keep accepted results and unfinished work distinct from a worker’s memory.
Retained outcomes + durable obligations + exact reads
History and durable obligations exist in source. Managed cross-agent handoff is planned; this is not universal conversational or vector memory.
Context Zoom#
Move from an overview to a record and its exact evidence.
Scoped Views + exact references + independent byte budgets
Local Turn Frames exist. Managed context zoom and full provider-request budgets are planned. Displayed JSON bytes are not model tokens.
Workflow Dependencies#
Replay a workflow’s History, read only: every version, the exact versions each step read, and what a correction reached.
Ordered membership + explicit dependencies + current authority
Versions, kept corrections, and dependency marking exist in source. Customer workflow management is planned. The replay is read only: it registers no schedules and invokes no adapters.
Scoped Access#
Explore access boundaries, expired authority, and denied reads.
Principal → authorized workspace → bounded exact read
Authorization controls are implemented in source. This synthetic decision is not a live IAM test, compliance certification, or proof of deployed isolation.
Reuse & Efficiency#
Distinguish batching, reusable inputs, and affected work from model caching.
Exact input comparison + bounded reads + dependency re-evaluation
Bounded reads and local comparison reuse exist. General calculation caching is planned. Fixture counts are not AWS cost, latency, or token-savings measurements.
Durable Recovery#
Follow an accepted result and the publication still owed after a failure.
Stable submission identity + accepted receipt + unfinished obligation
Recovery paths are implemented and tested offline. The example is not a live process-restart drill or a guarantee of exactly-once external effects.
Counts, bytes, and tokens have different meanings#
Context bytes are counted from the displayed fixture JSON. They do not measure a complete provider request or model tokens. Required evidence is never silently removed to satisfy the byte budget.
Efficiency counts describe the four fixture records and listed affected outputs. An unchanged record is not an observed cache hit. Batching, exact-input reuse, dependency re-evaluation, and model prompt caching are separate mechanisms. This demonstration contains no cost, latency, token-savings, or provider-cache measurement.
Explore without dragging or a mouse#
Use ordinary buttons and selects for every action. The dependency map exposes each record as a keyboard-focusable button. Inspector tabs support Left/Right, Home, and End. Status is written in text as well as color. There is no autoplay, and reduced-motion preferences are respected. A static guide remains available without JavaScript.
Follow the same example in a walkthrough#
The planned founder walkthrough can link each chapter to a public explorer selection. No video, live NFL feed, or live AgentCore demo is linked until that material has been produced and qualified. The current NFL scenario uses fictional teams and authored scores; it is not a current league result.