guest-grammar

Auditing host-guest boundaries requires enforcing explicit admission rules and hana shaping discipline to prevent leakage, ensuring parser, lowering, and fixture details are moved outward to sidecar surfaces to preserve the host invariant.

Explicit admission in guest-grammar defines clear boundaries between host and guest code, requiring admission blocks and sidecar surfaces to be specified in SKILL.md to maintain separation of concerns during generation or refinement.

Moving parser and lowering details outward involves shifting these implementation specifics to designated sidecar surfaces, restricting changes to specified carrier regions to keep the parent invariant small and maintainable.

Generating guest-grammar law surfaces requires applying hana shaping discipline and explicit admission blocks, ensuring changes remain limited to designated regions while preserving the host invariant throughout the crafting process.

Failing to preserve the host invariant occurs when explicit admission rules are not enforced or when parser, lowering, and fixture details leak across boundaries instead of being moved outward to sidecar surfaces.

Auditing guest-grammar blocks requires sidecar surfaces, explicit admission rules, and hana shaping discipline to be defined in SKILL.md and accompanying materials before enforcing host-guest boundary separation.