| permalink | /faq.html |
|---|---|
| title | FAQ |
Because those fields are not in v2.1.3 message schema. Valid message fields are:
content(required)id|priority|min|grow|shrink|strategy(optional layout)when(optional bool gate)tools(only in@system)
Invalid fields must raise F452.
No. @context is layout configuration (budget and optional defaults).
RAG context should be represented via @vars + message content.
Yes, in Hypervisor profile.
It must appear only as base expression of a @vars value (optionally followed by pipeline).
Invalid placement must raise F452.
No. FACET makes contract processing and request construction deterministic. Model generation remains provider/model-dependent.
F001/F002/F003: indentation/tabs/syntaxF451/F452: type or schema violationsF453: runtime input fails declared typeF601/F602: import sandbox/cycleF801/F803: disallowed mode/runtime behaviorF454/F455: policy deny vs guard undecidable
Core parses full syntax but rejects disallowed constructs with F801.
Examples: @input, interfaces, runtime-only behavior.
Always:
- all
@systemblocks - then all
@user - then all
@assistant
Within each role, resolved source order is preserved.
No. Layout may compress/truncate/drop flexible sections but must preserve canonical ordering.
sha256 over Resolved Source Form (imports expanded, NFC+LF normalized).
If policy exists:
sha256(JCS({ policy_version, policy: EffectivePolicyObject }))
Else null.
F454: deterministic deny (policy evaluated successfully)F455: guard could not deterministically evaluate (fail-closed)
Pure mode requires Level-1 cache-only execution.
Cache miss must raise F803.
String keys are allowed only in @meta.
Outside @meta, string-keyed map entries must raise F452.
Numeric list indexing is not standardized in v2.1.3.
It must raise F452 unless a namespaced host extension explicitly enables it.
Canonical JSON from Phase 5. It is provider-agnostic and deterministic by spec constraints.