guest-grammar

name	guest-grammar
description	Generate, compress, or audit guest-grammar surfaces under lar:///ha.ka.ba/@lares/api/v0.1/pono/guest-grammar. Keep the parent invariant small, preserve explicit admission, and move parser, lowering, and fixture detail outward.
allowed-tools	Read, Grep, Glob, Bash, Edit, Write

<<~� ? -> lar:///ha.ka.ba/@lares/api/v0.1/pono/guest-grammar/SKILL >>

uri-path = "ha.ka.ba/@lares/api/v0.1/pono/guest-grammar/SKILL"
file-path = "bags/@lares/api/v0.1/pono/guest-grammar/SKILL.md"
type = "text/x-memetic-wikitext"
confidence = 0.70
register = "CS"
manaoio = 0.68
mana = 0.74
manao = 0.80
role = "guest-grammar operational skill — admission audit, hana shaping, and sidecar split discipline"
covers = [
  "lar:///ha.ka.ba/@lares/api/v0.1/pono/guest-grammar"
]
constraints = [
  "S1: the parent invariant remains the admission law and this skill does not outrank it",
  "S2: guest work enters only through explicit host admission; ambient leakage does not count as lawful guest grammar",
  "S3: root primitives stay host-side and do not become guest-family proxies",
  "S4: hana keeps opener, optional priming payload, and guest body distinct",
  "S5: parser legality, lowering schemas, fixture execution, and long examples move outward before the parent swells"
]
skill-package-root = "packages/lares-core/memes/api/v0.1/pono/guest-grammar"
cacheable=true
retain = true

Guest-Grammar Skill

guest-grammar.md holds the law. This skill carries the working procedure.

<<~ ahu #load-contract >>

Load Contract

Keep these points active when the skill loads:

• the parent invariant binds explicit guest admission
• hana stays the canonical guest-work block when the work concerns data or code processing
• host primitives stay distinct from guest families
• local priming payload stays distinct from canonical meme identity payload
• graceful local degradation beats flattering collapse or silent fabrication
• the smallest lawful intervention beats a grand rewrite

<<~/ahu >>

<<~�>>

<<~ ahu #workflow-contract >>

Workflow Contract

Use this skill to:

1. draft a guest-grammar law surface
2. audit host-guest boundary discipline
3. shape a lawful hana block
4. split parser, lowering, or fixture detail into outward surfaces

Working order:

1. read the carrier or target region fully
2. identify the host surface and the admitted guest site
3. classify material into admission law, hana shape, ownership boundary, degradation, lowering, or fixtures
4. keep only invariant admission law in the parent
5. move checklist, examples, and execution detail outward
6. verify that the host still reads clearly when the guest region fails

Do not:

• treat ambient punctuation as lawful guest admission
• let a root primitive quietly stand in for a guest family
• move canonical identity payload into hana
• hide malformed guest work behind a fake success path
• burden the parent with full parser or render implementation detail

<<~/ahu >>

<<~ ahu #trigger >>

Trigger

Use this skill when the request asks to:

• create or revise guest-grammar law
• audit a hana worksite
• protect root primitives from guest overload
• separate admission law from parser or render detail
• define graceful degradation for guest work

Prefer another surface when the work concerns only:

• root authoring semantics under memetic-wikitext
• pure parser legality with no admission-law change
• pure render lowering with no host-guest boundary change

<<~/ahu >>

<<~ ahu #ooda-ha >>

✶ read host and guest boundaries first and observe the actual admission surface ⏿ sort admission law, ownership boundary, degradation pressure, and implementation detail by where they belong ◇ choose the smallest lawful split and the most honest posture for the target region ▶ write the lightest useful change while keeping guest entry explicit and hana shape crisp ⤴ verify explicit admission and bounded degradation without hiding malformed or unsupported guest work ↺ name the remaining residue plainly, including what still lacks a lawful downstream home

<<~/ahu >>

<<~ ahu #observe >>

✶ Observe

Read the host surface before changing it.

Look for:

• explicit guest entry
• hana opener and closer
• optional priming payload
• guest body continuity
• host primitive drift
• parser legality detail
• render lowering detail
• fixture or conformance backlog

Preserve the difference between admitted, malformed, unsupported, and absent guest regions.

<<~/ahu >>

<<~ ahu #orient >>

⏿ Orient

Sort findings into these buckets:

• admission-law
• hana-shape
• ownership-boundary
• degradation
• parser-or-lowering-detail
• fixtures-or-docs-residue

Orientation rule:

• admission-law, hana-shape, and ownership-boundary stay nearest the parent
• degradation stays only at the level of invariant fallback pressure
• parser-or-lowering-detail moves outward first
• fixtures-or-docs-residue belongs in docs or later subtype surfaces

<<~/ahu >>

<<~ ahu #decide >>

◇ Decide

Choose the smallest lawful shape:

• parent only, when admission law already reads clearly
• parent + SKILL.md, when audit or shaping procedure needs room
• parent + docs, when examples and boundary notes crowd the root
• parent + SKILL.md + docs, when law, procedure, and explanation all need different rooms

Then choose one honest posture for the target region:

• not admitted
• admitted but degraded
• admitted and bounded

Do not round up from aspiration to law.

<<~/ahu >>

<<~ ahu #act >>

▶ Act

When writing or revising:

• keep the parent compact
• keep guest admission explicit
• keep hana block structure crisp
• move full canonical forms and fixtures into sidecars
• keep ownership lines short and load-bearing
• link the split surfaces with loulou

Canonical Hana Shape

<<~ hana #work >>
```toml
grammar = "x-tiddlywiki-filter"
profile = "canonical"
context = "+currentMeme"
degrade = "no-op"
result-shape = "set"
```

[all[sigils]links:to[+currentMeme]]
<<~/hana >>

<<~/ahu >>

<<~ ahu #verify >>

⤴ Verify

Before closing, check:

• opener and file-path agree with the carrier
• the parent invariant remains small enough to reload easily
• hana keeps opener, payload, and body distinct
• docs state non-law posture near the top
• no host primitive got reassigned to guest-family work
• parser and lowering detail no longer crowd the parent
• outward links name real adjacency or real backlog

<<~/ahu >>

<<~ ahu #aftermath >>

↺ Aftermath

Close by naming:

• what stayed in the parent
• what left for the sidecars
• whether the target region now counts as not admitted, admitted but degraded, or admitted and bounded
• which next change would improve the region honestly
• what still lacks a lawful downstream home

<<~/ahu >>

<<~ ahu #edges >>

Edges

<<~ loulou lar:///ha.ka.ba/@lares/api/v0.1/pono/guest-grammar >> <<~ loulou lar:///ha.ka.ba/@lares/docs/pono/guest-grammar >>

<<~ pranala #implements-meme ? -> lar:///ha.ka.ba/@lares/api/v0.1/pono/meme family:control role:implements >> <<~ pranala #implements-loci ? -> lar:///ha.ka.ba/@lares/api/v0.1/pono/loci family:control role:implements >> <<~/ahu >>

<<~�>>

<<~� -> ? >>