Clarify synthetic acceptance and live-runtime gate
Browse files
README.md
CHANGED
|
@@ -21,6 +21,11 @@ matching model/tokenizer identity, tensor geometry, RoPE semantics, layout, and
|
|
| 21 |
sequence position. Cross-family handoff requires a trained and evaluated
|
| 22 |
translator.
|
| 23 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 24 |
The optional `DOMCAP1` sidecar pack, **Analytics Hotshot**, contains a compact expert briefing,
|
| 25 |
trusted host-tool identifiers, a source policy, and evaluation probes. The
|
| 26 |
portfolio fetches the JSON artifact after a visitor elects to load the pack,
|
|
|
|
| 21 |
sequence position. Cross-family handoff requires a trained and evaluated
|
| 22 |
translator.
|
| 23 |
|
| 24 |
+
The current acceptance run uses deterministic synthetic payload bytes. It
|
| 25 |
+
validates the KVC1 container and failure boundaries, not live cache extraction
|
| 26 |
+
or reinjection. Source-runtime extraction and same-family reload are the next
|
| 27 |
+
integration gates.
|
| 28 |
+
|
| 29 |
The optional `DOMCAP1` sidecar pack, **Analytics Hotshot**, contains a compact expert briefing,
|
| 30 |
trusted host-tool identifiers, a source policy, and evaluation probes. The
|
| 31 |
portfolio fetches the JSON artifact after a visitor elects to load the pack,
|