Private
Public Access
0
0
Files
manual_slop/conductor/tracks/chunkification_optimization_20260608_PLACEHOLDER/state.toml
T
conductor-tier2 816e9f2f5c conductor(track): chunkification_optimization_20260608_PLACEHOLDER - 1-page contingency document
The user's third correction this session changed the framing
from "build a stateful C extension" to "wait for a hard constraint,
then build a request/response blob pipeline." This commit creates
a 1-page contingency document (no plan.md, no implementation)
that captures:

- The threshold: "only worth it under a hard constraint that
  no existing Python package can solve"
- The shape when activated: subprocess-launch C11 binary with
  request/response blob wire format (NOT stateful CPython C
  extension)
- The 2 cited candidates (markdown parsing into aggregate markdown,
  context snapshot processing) are NOT currently bottlenecks per
  src/aggregate.py:380-454 (pure-Python string concat, zero
  third-party markdown deps in pyproject.toml:6-27) and
  src/history.py:1-141 (bounded ~500KB at 100-snapshot capacity,
  debounced)
- The SSDL digest's Technique 5 "Assume-away (Xar)" in §2.2 +
  "Xar-style chunked arrays" recommendation in §5.2 pre-support
  this track

Files (4 total, 227+ lines of contingency document):
- conductor/tracks/chunkification_optimization_20260608_PLACEHOLDER/spec.md
- conductor/tracks/chunkification_optimization_20260608_PLACEHOLDER/metadata.json
- conductor/tracks/chunkification_optimization_20260608_PLACEHOLDER/state.toml
- conductor/tracks/chunkification_optimization_20260608_PLACEHOLDER/index.md

Cross-references added:
- docs/reports/computational_shapes_ssdl_digest_20260608.md (the
  SSDL digest is the theoretical foundation; explicitly cited in
  the spec's §6.1 "SSDL alignment" and in metadata.json external)
- docs/reports/c11_python_interop_assessment_20260608.md (the v1+v2
  assessment; explicitly cited in spec's §6 See Also)

No code modified. Track does NOT appear in the active queue
of conductor/tracks.md; appears in the Backlog / Contingency
section as a reference, not a commitment.

Activation criteria (per metadata.json):
1. Profiling shows a real bottleneck in a target code path
2. The bottleneck cannot be solved with existing Python packages
3. The user explicitly approves activation

Without all 3, this track stays deferred. Default action is don't.
2026-06-08 23:40:27 -04:00

72 lines
4.4 KiB
TOML

# Track state for chunkification_optimization_20260608_PLACEHOLDER
# Contingency document — does NOT produce code or implementation tasks
# Promoted to active track when the activation criteria in metadata.json are met
[meta]
track_id = "chunkification_optimization_20260608_PLACEHOLDER"
name = "Chunkification Optimization (C11 Pipeline Contingency)"
status = "deferred" # contingency only; no implementation
current_phase = 0 # 0 = not started; will become 1 when promoted to active
last_updated = "2026-06-08"
[blocked_by]
# Contingency: cannot start until these are true
hard_constraint_profiling_evidence = "Profiling must show a real bottleneck that no existing Python package can solve"
user_approval_for_activation = "User must explicitly say 'activate this track' before any code is written"
[blocks]
# Contingency: this track blocks nothing (it's a future option, not a dependency)
# No entries.
[user_corrections_log]
# Two user-corrections shaped the v2 framing of this contingency
2026-06-08_1 = "v1 framing (stateful C extension) revised to v2 (request/response blob pipeline). User: 'the python would have to define the payload in a simple text or binary format as the request and then the extension pipeline in C11 would do the ops and provide the output in another binary or text blob/s.' This is the SUBPROCESS model, not a stateful CPython C extension."
2026-06-08_2 = "v1 'build it now' revised to 'build only when hard constraint surfaces'. User: 'only worth it if I reach a hard constraint that I cannot solve with an existing python package.' The 2 cited targets (markdown parsing, snapshot processing) are not currently bottlenecks per src/aggregate.py:380-454 and src/history.py:1-141."
[tasks]
# Contingency: no implementation tasks until activation
# When activated, copy the activation plan from spec.md §2 into a new plan.md
t_contingency_01 = { status = "completed", commit_sha = "", description = "Write 1-page contingency spec.md (this file's parent)" }
t_contingency_02 = { status = "completed", commit_sha = "", description = "Write metadata.json with activation criteria + shape_when_activated" }
t_contingency_03 = { status = "completed", commit_sha = "", description = "Write state.toml with deferred status + user_corrections_log" }
t_contingency_04 = { status = "completed", commit_sha = "", description = "Write index.md" }
t_contingency_05 = { status = "pending", commit_sha = "", description = "Add entry to conductor/tracks.md (post-commit, in 'Contingency / Future' section)" }
# Activation-gated tasks (do not start without explicit user approval):
t_activate_01 = { status = "pending", commit_sha = "", description = "[ACTIVATION-GATED] Profile target code path; confirm hard constraint" }
t_activate_02 = { status = "pending", commit_sha = "", description = "[ACTIVATION-GATED] Try existing Python packages first (markdown-it-py / pickle / msgspec / etc.)" }
t_activate_03 = { status = "pending", commit_sha = "", description = "[ACTIVATION-GATED] If existing packages don't work, define wire format (text v1, binary v2)" }
t_activate_04 = { status = "pending", commit_sha = "", description = "[ACTIVATION-GATED] Write C11 pipeline binary in duffle.h style" }
t_activate_05 = { status = "pending", commit_sha = "", description = "[ACTIVATION-GATED] Write Python subprocess wrapper" }
t_activate_06 = { status = "pending", commit_sha = "", description = "[ACTIVATION-GATED] Write tests in tests/test_chunka_c11.py" }
t_activate_07 = { status = "pending", commit_sha = "", description = "[ACTIVATION-GATED] Build + deploy (uv + pyproject.toml hook)" }
t_activate_08 = { status = "pending", commit_sha = "", description = "[ACTIVATION-GATED] Profile: confirm C11 path is faster than Python baseline" }
[verification]
# Contingency verification is artifact presence only
spec_md_exists = true
metadata_json_exists = true
state_toml_exists = true
index_md_exists = true
# Activation criteria documented
activation_criteria_documented = true
# Current targets analyzed and found NOT to be bottlenecks
markdown_target_analyzed = true # src/aggregate.py:380-454; pyproject.toml:6-27
snapshot_target_analyzed = true # src/history.py:1-141
# v1 + v2 corrections recorded
v1_stateful_c_extension_revised = true
v2_request_response_pipeline_adopted = true
# No code modified
no_code_modified = true
[status]
# Contingency only; "deferred" means the track is documented but not in active work
status = "deferred (contingency documented; will activate when hard constraint surfaces)"