live: heartbeat sync 2026-10-18T16:47:59-07:00 (Refs #11)

This commit is contained in:
Frank committed 2026-10-18 16:47:59 -07:00
1 parent a550db6027
commit 979e9ef711
173 files changed
+3844 -57

No files matched your search

@@ -0,0 +1,19 @@
## Runtime Context
- **Tool call execution**: user-perceived failures require confirmation; when `regression=true` is flagged, re-execute with contextual resolution.
- **Power failure**: system reboot caused by power failure.
## Model Configuration
- **KV context**: 4×200,000 fp8 quantized kv slots.
- **Calibration context**: fp8.
- **Concurrent streams**: 3.
- **Expert configuration**: 49,152 GPTQ w4 experts (10M-token calibration on engine 1.2.0) + 24 bf16-protected experts/layer (energy-share pattern: bf16-protected experts and their resource allocation within a card's VRAM budget) within 29,120 MiB/card ceiling; 47.7 GiB n-gram copy pinned to host RAM.
## Deployment Testing Policy
- **Emergency bypass**: E2E gate may be skipped with `--skip-e2e` flag during outages; normal flow requires all three gates including the final Playwright e2e suite.
@@ -0,0 +1,23 @@
## Service Availability
- **frank-archon**: must be running (active deployment requirement).
## Deployment Testing Policy
- **Emergency bypass**: E2E gate may be skipped with `--skip-e2e` flag during outages; normal flow requires all three gates including the final Playwright e2e suite.
## Calibration
- **Concurrent streams**: 3.
## Problem Domain
- **Core scope**: tracking user identity for deployed LLMs.
## Research Quality
- **Exhaustive and ambitious**: research output must cover the full solution space with depth and breadth.
## Solution Evaluation
- **Comparative approach**: evaluate multiple tracking solutions rather than committing to a single implementation upfront.
@@ -0,0 +1 @@
{"v":1,"kind":"product_decision","statement":"Recent changes are accessible via an open pull request","source":"explicit_user","evidence":"where is the open pull request?","friction":{"corrective":false,"regression":false,"subtle":false},"sessionId":"01a1391f-7c35-77ea-860c-ecc018ab85a9","ts":1792009661330}
@@ -0,0 +1 @@
{"v":1,"kind":"correction","statement":"The current session is distinct from the one previously referenced","source":"explicit_user","evidence":"I'm in the wrong session","friction":{"corrective":true,"regression":false,"subtle":false},"sessionId":"01a1391f-7c35-77ea-860c-ecc018ab85a9","ts":1792009849983}
@@ -0,0 +1 @@
{"v":1,"kind":"product_decision","statement":"PR #1 is discarded","source":"contextual_resolution","evidence":"toss the pr made this session","friction":{"corrective":false,"regression":false,"subtle":false},"sessionId":"01a1391f-7c35-77ea-860c-ecc018ab85a9","ts":1792009890268}
@@ -0,0 +1,10 @@
{
"v": 1,
"lastConsolidatedAt": 1792009612039,
"lastResult": {
"at": 1792009612039,
"sessions": 1,
"deltas": 1,
"model": "frank-zealot"
}
}
@@ -0,0 +1,5 @@
## Terminology
- **Law**: when describing a mechanism, use general mechanism or pattern rather than specific events or project-specific references.
- **Substantive rewriting**: when modifying documentation or comments, explain the mechanism and rationale, not merely swap terms. Phrase-level replacements without explanatory context are insufficient.