Turn Record · May 22, 2026

Add Options Anatomy Explainer

Added a standalone docs/anatomy.html reference page that explains the full lifecycle of an options print, from ingest and signal gating through flow packet construction, smart-money scoring, classifier hits, alerts, and API/live consumption. The page is styled to match Islandflow’s product register and layered so exec, mixed technical, and operator-level readers can all use the same artifact.

Beads islandflow-hpf
Artifact docs/anatomy.html
Register Product, evidence-console styling
Secondary Change Regenerated docs/index.html

Summary

The repo now includes a reusable explainer page for one of the most important pieces of Islandflow’s mental model: how a raw or synthetic options print turns into visible tape, a flow packet, and sometimes a smart-money or alert event. Instead of scattering that explanation across chat answers and source code, the new page centralizes the pipeline in a designed HTML document that can be browsed directly under docs/.

Primary outcome: the new page makes the option-print pipeline legible at three reading depths without forcing someone to reconstruct the architecture from service code.

Changes Made

  • Added docs/anatomy.html as a standalone explainer page titled The Anatomy of an Options Print and Smart Money.
  • Built a large flow-chart section that distinguishes the common tape path from the signal-to-packet-to-smart-money branch.
  • Layered the page into executive, mixed technical, and operator-level explanations so one artifact works for multiple audiences.
  • Included subject/table mapping, annotated sequence detail, synthetic-mode notes, and code anchors back into the real repo.
  • Regenerated docs/index.html so the new explainer is discoverable from the existing docs index.

Context

The user asked for a true flow-chart explanation of what happens when options tape comes in under normal market scenarios and when smart-money behavior is detected, with the important caveat that the current environment is using synthetic prints. The repo already had the implementation details, but not a clear product artifact that unified ingest, compute, storage, bus subjects, and API/live consumption into one readable document.

Because Islandflow’s UI language is already defined as an “evidence console,” the new page needed to feel operational and precise rather than like a generic landing page or a decorative infographic.

Important Implementation Details

Information architecture

  • The page starts with a semantic legend and a visual flow board so readers can build the correct mental model before diving into prose.
  • The explanation then deepens in three layers: executive read, mixed technical walkthrough, and operator/code-level detail.
  • The normal tape path and the smart-money path are split explicitly so readers do not confuse raw tape visibility with compute-derived inference.

Design choices

  • The visual treatment follows the repo’s product register: dark, stable, evidence-first, amber used as a sparse signal, monospace labels for pipeline semantics.
  • The flow chart is pure HTML and CSS, not a JavaScript diagram dependency, so the page remains portable and straightforward to keep in sync with the repo.
  • docs/index.html was regenerated with the existing script so the page participates in the current docs navigation surface instead of becoming a hidden one-off.

Relevant Diff Snippets

These snippets are rendered with the Diffs library from diffs.com, with a plain-text fallback kept inline.

docs/anatomy.html: new explainer page and flow-board structure

Plain-text fallback 
+ Added docs/anatomy.html
+ Product-register dark evidence-console styling
+ Main flow chart with common path, tape-only branch, and smart-money branch
+ Layered explanation sections for executive, mixed technical, and operator audiences
+ Subject map, annotated sequence, synthetic mode notes, and code anchors

docs/index.html: regenerated docs surface with new entry count

Plain-text fallback 
- 35 files shown
+ 47 files shown
- root/general counts from prior docs set
+ updated counts after regenerating the index, including the new anatomy explainer entry

Expected Impact for End-Users

  • Teammates and operators now have a single place to understand why a print can appear on tape without ever becoming a smart-money event.
  • The synthetic-print caveat is captured directly in the artifact, which should reduce confusion when debugging or demoing the current environment.
  • The docs surface becomes more useful as a living product reference, not just a collection of turn records and plans.

Validation

  • Generated the new page at docs/anatomy.html and verified the title and major sections are present.
  • Regenerated the docs index with node scripts/generate-docs-index.mjs, which completed successfully and reported 47 entries.
  • Confirmed the new explainer page is included in the docs surface by regenerating docs/index.html.
1 new reusable explainer page
47 docs index entries after regeneration
3 reader depth layers on the page

Issues, Limitations, and Mitigations

  • The page is intentionally hand-authored HTML rather than a generated diagram artifact. That keeps it portable, but it also means future pipeline changes should update this page manually.
  • The docs index regeneration reflects the full current docs/ tree, so the visible counts changed by more than one file compared with the previously committed index.
  • This validation pass verified structure and generation success, but did not include a browser-rendered visual QA step against multiple viewport sizes.

Follow-up Work

  • Add reciprocal links from more domain-specific docs such as smartmoney.md back to docs/anatomy.html.
  • Consider a second reference page focused specifically on one concrete synthetic example, from a burst of prints to the final alert payload.
  • If the flow-packet feature set evolves, keep the anatomy page in lockstep with those changes so it remains a trustworthy operator reference.