diff --git a/.gitattributes b/.gitattributes
new file mode 100644
index 00000000..27c05aeb
--- /dev/null
+++ b/.gitattributes
@@ -0,0 +1,2 @@
+# Taken requires a blank line after every Org subtree, including EOF.
+.taken/*.org whitespace=-blank-at-eof
diff --git a/.taken/current.org b/.taken/current.org
index 04ee4a12..b791743d 100644
--- a/.taken/current.org
+++ b/.taken/current.org
@@ -288,3 +288,139 @@
 - [ ] preserve incremental appends, view changes, and cache invalidation
 - [ ] test sum conservation across zoom levels and partial edge buckets
 - [ ] profile the cumulative path against the existing M4 implementation
+
+** TODO review and save the Trend Calculus prototype
+:PROPERTIES:
+:ID: piker-trend-calculus-prototype-review
+:CREATED: [2026-10-05]
+:CARRIED: 0
+:REPO: /home/goodboy/repos/piker
+:AI_HARNESS: codex
+:AI_WORKTREE: /home/goodboy/repos/piker
+:AI_BRANCH: trend_calc_on_jev
+:ISSUE: https://github.com/pikers/piker/issues/187
+:END:
+[[file:/home/goodboy/repos/piker/docs/trend_calculus.rst][Research and prototype guide]]
+- [ ] Regenerate and review six Trend Calculus behavior boundaries
+  on trend_calc_on_jev after workflow commit f148fbcc on
+  moar_ai_skillz lands; retain source/test pairs and inspect every
+  message before saving.
+- [ ] Run each boundary check from the pinned package and the final
+  safe regression sequence; the working-tree offline suite passed 253
+  tests.
+- [ ] Qualify one selected live source through startup, quiet bars,
+  skipped wakeups, history repair, replay and owner cancellation.
+- [ ] Coordinate inherited stream/backfill work with
+  [[id:piker-fsp-backfill-sync-review-and-commit][the existing FSP synchronization task]].
+
+** TODO qualify Jev regime judgments against real responses
+:PROPERTIES:
+:ID: piker-jev-live-regime-qualification
+:CREATED: [2026-10-05]
+:CARRIED: 0
+:REPO: /home/goodboy/repos/piker
+:AI_HARNESS: codex
+:AI_WORKTREE: /home/goodboy/repos/piker
+:AI_BRANCH: trend_calc_on_jev
+:END:
+[[file:/home/goodboy/repos/piker/docs/trend_calculus.rst][Research and prototype guide]]
+- [ ] Once TYPESAFE_API_KEY is available and a live request is
+  authorized, send one small synthetic multi-timeframe request
+  through the HTTPX/Trio client.
+- [ ] Verify the documented request/response schema, model identity,
+  distributions, usage, errors and measured end-to-end latency.
+- [ ] Evaluate useful regime labels and confidence on held-out trend
+  snapshots, including flat, reversing, aligned and conflicting
+  timeframes.
+- [ ] Measure sustained pacing, coalescing, source freshness and cost
+  before enabling realtime judgments.
+- [ ] Consider an SDK AnyIO port or Trio backend only after the
+  direct HTTP prototype demonstrates useful classifications.
+
+** TODO connect finalized trends to the Jev provider-service
+:PROPERTIES:
+:ID: piker-jev-provider-service-integration
+:CREATED: [2026-10-05]
+:CARRIED: 0
+:REPO: /home/goodboy/repos/piker
+:AI_HARNESS: codex
+:AI_WORKTREE: /home/goodboy/repos/piker
+:AI_BRANCH: trend_calc_on_jev
+:END:
+[[file:/home/goodboy/repos/piker/docs/trend_calculus.rst][Research and prototype guide]]
+- [ ] Obtain the separate system-1 provider-service repository or
+  interface and identify its input, output, lifecycle and ownership
+  contracts.
+- [ ] Adapt serve_regimes and RegimeClassifier to the service nursery
+  and typed publication interface without mixing model labels into
+  deterministic trend state.
+- [ ] Configure market, periods, model, credentials, request pacing,
+  evidence retention and freshness limits explicitly.
+- [ ] Verify reconnect, revision/gap invalidation, backpressure,
+  stale-response rejection and shutdown with the actual service.
+
+** TODO recover Pine source and check Trend Calculus parity
+:PROPERTIES:
+:ID: piker-trend-calculus-pine-parity
+:CREATED: [2026-10-05]
+:CARRIED: 0
+:REPO: /home/goodboy/repos/piker
+:AI_HARNESS: codex
+:AI_WORKTREE: /home/goodboy/repos/piker
+:AI_BRANCH: trend_calc_on_jev
+:ISSUE: https://github.com/pikers/piker/issues/103
+:END:
+[[file:/home/goodboy/repos/piker/docs/trend_calculus.rst][Research and prototype guide]]
+- [ ] Recover the human's Pine implementation and record its
+  provenance/version alongside the pinned Lua and Scala research.
+- [ ] Compare startup seeding, extrema ties, FHLS splitting, opposing
+  pivots and recursive reversal orders.
+- [ ] Add independent fixtures for meaningful semantic differences;
+  distinguish extremum time from confirmation time and mutable-bar
+  previews.
+
+** TODO qualify multitimeframe pivots and regime annotations
+:PROPERTIES:
+:ID: piker-trend-regime-chart-qualification
+:CREATED: [2026-10-05]
+:CARRIED: 0
+:REPO: /home/goodboy/repos/piker
+:AI_HARNESS: codex
+:AI_WORKTREE: /home/goodboy/repos/piker
+:AI_BRANCH: trend_calc_on_jev
+:END:
+[[file:/home/goodboy/repos/piker/docs/trend_calculus.rst][Research and prototype guide]]
+- [ ] Inspect actual 1/5/15-second layers and hover information on a
+  selected live market; compare confirmed pivots and regime
+  boundaries to finalized source evidence.
+- [ ] Verify chart-axis placement, gaps, revisions, hidden charts,
+  duplicate cached feeds and owner-scoped cleanup.
+- [ ] Qualify model rectangles at response receipt and expiry,
+  including stale classifications and source-segment changes.
+- [ ] Measure quiet-bar display delay before deciding whether
+  publication needs an explicit output notification.
+- [ ] Coordinate shared history-overlay lifecycle with the existing
+  chart-local gap overlay follow-ups; route any annotation IPC
+  factoring to the existing typed-dialog task.
+
+** TODO qualify a native subsecond source for trend regimes
+:PROPERTIES:
+:ID: piker-trend-native-subsecond-sampling
+:CREATED: [2026-10-05]
+:CARRIED: 0
+:REPO: /home/goodboy/repos/piker
+:AI_HARNESS: codex
+:AI_WORKTREE: /home/goodboy/repos/piker
+:AI_BRANCH: trend_calc_on_jev
+:END:
+[[file:/home/goodboy/repos/piker/docs/trend_calculus.rst][Research and prototype guide]]
+- [ ] Define the required high-frequency periods and producer
+  contract; the numeric/MTF APIs accept fractional periods but the
+  current native clock uses whole seconds.
+- [ ] Extend or select the source/sampler time grid before enabling
+  subsecond chart/service periods; retain strictly increasing
+  coordinates and complete aligned buckets.
+- [ ] Measure compute, SHM publication, service latency and chart
+  refresh under the selected cadence, including gaps, replay and
+  cancellation.
+
diff --git a/ai/prompt-io/codex/20261005T230013Z_9555e20c_trend_followups_d48a77_prompt_io.md b/ai/prompt-io/codex/20261005T230013Z_9555e20c_trend_followups_d48a77_prompt_io.md
new file mode 100644
index 00000000..f8144e7d
--- /dev/null
+++ b/ai/prompt-io/codex/20261005T230013Z_9555e20c_trend_followups_d48a77_prompt_io.md
@@ -0,0 +1,58 @@
+---
+created_at: 2026-10-05T23:00:13.353081+00:00
+generated_by:
+  harness: codex
+  provider: OpenAI
+git_ref: 9555e20c
+scope: data
+substantive: true
+raw_file: 20261005T230013Z_9555e20c_trend_followups_d48a77_prompt_io.raw.md
+---
+
+## Prompt
+
+The human asked to capture all ongoing Trend Calculus/Jev follow-ups
+in Taken, supplied the federated_project_stores worktree, and then
+requested a complete commit plan for that branch. They confirmed
+that workflow configuration already exists on moar_ai_skillz and
+asked why the earlier trend package duplicated it.
+
+## Response summary
+
+Resolved the registered Piker corpus and unique structural parent.
+Used Taken's guarded whole-document save to append six identified
+TODO tasks and 24 unchecked items. Preserved every prior byte,
+existing state, property and order. Linked the existing FSP review
+instead of duplicating it and kept annotation IPC follow-ups with
+the existing task. Recorded known harness/worktree/branch provenance.
+
+Corrected only the new prototype-review task's prose to require the
+existing f148fbcc/moar_ai_skillz workflow dependency and regenerate
+six Trend Calculus behavior boundaries. No task marker was changed.
+Added a whitespace attribute limited to .taken Org documents so the
+required final empty subtree separator passes standard Git checks.
+No other workflow configuration is included in this commit package.
+
+## Verification
+
+Taken lint previously passed on the saved corpus and standard Git
+whitespace checks pass with the path-scoped Org attribute. Saved
+bytes were checked against the guarded candidate; all original
+corpus content and state markers are intact. The commit package
+selects a read-only lint against its exact boundary store, with
+application tests excluded for this data-only change. That check
+remains pending until package execution; no earlier whole-worktree
+result is claimed as an exact-boundary reusable pass.
+
+## Human edits
+
+The human authorized loading the registered store and requested
+planning, not execution. Their workflow-history correction directly
+changed the new review task. Existing human tasks remain unaccepted;
+no commits, pushes, rebases, mainlining or existing-state changes
+were performed. The main checkout's staged content was preserved.
+
+## Files changed
+
+- `.taken/current.org`
+- `.gitattributes`
diff --git a/ai/prompt-io/codex/20261005T230013Z_9555e20c_trend_followups_d48a77_prompt_io.raw.md b/ai/prompt-io/codex/20261005T230013Z_9555e20c_trend_followups_d48a77_prompt_io.raw.md
new file mode 100644
index 00000000..7f0b2d71
--- /dev/null
+++ b/ai/prompt-io/codex/20261005T230013Z_9555e20c_trend_followups_d48a77_prompt_io.raw.md
@@ -0,0 +1,52 @@
+---
+created_at: 2026-10-05T23:00:13.353081+00:00
+generated_by:
+  harness: codex
+  provider: OpenAI
+git_ref: 9555e20c
+scope: data
+substantive: true
+---
+
+## Human instruction (verbatim)
+
+after this pass i want us to start loading our taken store with all the ongoing / todos/ follow ups anyway - we can hash it all out there.
+
+it's on another unmerged wkt we have to mainline, not sure what the
+best stopgap for that is rn but the existing taken is here,
+wkt/federated_project_stores
+
+can we do a $commit-plan for that wkt branch with this stuff then as
+well? i'm going to try and get it landed to main asap so we can start
+always updating it directly from our working branch/wkt.
+
+uhh isn't this already in f148fbcc and the moar_ai_skillz branch??
+
+## Captured assistant output (verbatim)
+
+The style pass and seven-commit package are finished. I added
+six follow-up tasks with 24 unchecked items to the registered
+Taken corpus and verified that all prior content is unchanged.
+Taken lint passes.
+
+You’re right: the three `.ai` files are byte-for-byte identical
+to `f148fbcc` on `moar_ai_skillz`. That commit isn’t in this
+checkout or local `main` yet, but I should have treated it as
+an existing branch dependency, not proposed a duplicate commit.
+
+I’m withdrawing that workflow step from the Trend Calculus plan.
+Those files are now staged here; I’ll leave your index untouched.
+
+## Data/configuration pointers
+
+> `git diff HEAD~1..HEAD -- .taken/current.org`
+
+> `git diff HEAD~1..HEAD -- .gitattributes`
+
+These pointers name the completed one-boundary commit after human
+review/execution. The prepared package captures the pending delta.
+Six identified tasks retain all existing states and record prototype
+review, live Jev qualification, service wiring, Pine parity, chart
+qualification and native subsecond source work. A narrow Org
+attribute permits Taken's required blank separator at EOF while
+retaining other whitespace diagnostics. No Git commit ran.