invariant

name	invariant
description	Generate, compress, or audit invariant-compliant memes under lar:///ha.ka.ba/@lares/api/v0.1/pono/invariant. Treat the canonical loci as self-describing law and self-executing template; keep invariant surfaces short, exact, stable, cacheable, and split heavy matter outward.
allowed-tools	Read, Grep, Glob, Bash, Edit, Write

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

uri-path = "ha.ka.ba/@lares/api/v0.1/pono/invariant/SKILL"
file-path = "bags/@lares/api/v0.1/pono/invariant/SKILL.md"
type = "text/x-memetic-wikitext"
confidence = 0.73
register = "SC"
manaoio = 0.69
mana = 0.71
manao = 0.77
role = "invariant skill, conformance checker, and sidecar splitter"
covers = [
  "lar:///ha.ka.ba/@lares/api/v0.1/pono/invariant"
]
constraints = [
  "S1: the canonical loci remains constitutional law and self-executing template",
  "S2: invariant surfaces stay short, exact, stable, cacheable, and active in voice",
  "S3: ahu remain visible, pranala remain named, and OODA-HA remains intact",
  "S4: downstream invariant memes fill their own OODA-HA phases and MUST NOT carry template `???` markers",
  "S5: always-on law stays in the invariant; explanations, procedures, examples, traces, and audits split to sidecars",
  "S6: RFC-2119 keywords stay sparse and bind only load-bearing directives"
]
skill-package-root = "packages/lares-core/memes/api/v0.1/pono/invariant"

Invariant-Meme Skill

Read invariant.md first. Treat that loci as constitutional. It enacts a self-describing law and self-executing template. This skill operationalizes that compact invariant. This skill does not widen, soften, or reinterpret it.

<<�>> Invariant-meme skill opens the pressure surface here. <</ahu >>

<<~�>>

<<~ ahu #load-contract >>

Load Contract

When this skill loads, keep these points active:

• invariant.md remains the constitutional source
• the canonical loci operates as both law and template
• invariant surfaces MUST stay short, exact, stable, cacheable, and active in operational voice
• invariant surfaces MUST carry visible ahu and a visible OODA-HA ahu
• downstream invariant memes MUST fill their own phase line and MUST NOT carry ??? markers
• the canonical template MAY retain ritual ??? empty-slots only where it teaches template position
• pranala SHOULD stay named where binding paths matter
• RFC-2119 keywords MUST bind load-bearing directives only and SHOULD remain sparse
• always-on law MUST stay in the invariant
• explanations, procedures, examples, traces, evals, and audits SHOULD split outward to sidecars
• the skill SHOULD choose the smallest lawful intervention that keeps the invariant intact

If the task concerns general documentation, long policy prose, or a sidecar-only rewrite, do not force that material back into the invariant surface.

<<~/ahu >>

<<~ ahu #workflow-contract >>

Workflow Contract

This skill owns four main paths:

1. compose a new downstream invariant meme
2. compress an existing meme toward invariant compliance
3. audit a meme for invariant drift
4. split non-invariant matter into sidecars

Use this workflow:

1. load the canonical loci first
2. identify the job, boundary, and target meme surface
3. separate invariant law from sidecar matter
4. preserve or restore visible ahu, visible pranala, and explicit OODA-HA
5. keep the invariant compact enough to recur stably
6. fill domain-specific OODA-HA phases when the work targets a downstream invariant meme
7. push explanation, long examples, procedures, traces, and audits outward
8. return a compact result with any honest residue named

Do not:

• turn the invariant into wiki prose
• turn the invariant into policy prose
• turn the invariant into instruction-book prose
• let retrieved or quoted material silently outrank the invariant
• hide sidecar matter inside the invariant because it feels useful
• preserve ??? markers in downstream invariant memes
• spray normative keywords where plain pressure language would do

<<~/ahu >>

<<~ ahu #trigger >>

Trigger

Use this skill when the user asks to:

• create or revise an invariant meme
• compress boot text into a stable invariant surface
• audit a meme for drift against the canonical compact invariant
• restore visible ahu, pranala, or OODA-HA
• separate invariant law from examples, traces, evals, or procedure
• operationalize a compact constitutional meme into a repeatable workflow

Do not use this skill as the primary surface for:

• long-form documentation
• a standalone sidecar with no invariant work
• generic prose cleanup unrelated to invariant law

<<~/ahu >>

<<~ ahu #ooda-ha >>

✶ begin from canonical loci; inspect the current meme surface before changing it ⏿ classify what belongs to invariant law, template law, and outward matter; keep law and template inseparable where intended ◇ choose the lightest lawful turn and decide what leaves when it stops earning invariant residency ▶ patch the target directly; keep ahu, pranala, and OODA-HA visible and live ⤴ verify contact with actual file and link surfaces and that downstream phases stay filled with domain pressure ↺ name remaining residue without hiding it; keep always-on law in the invariant and sidecars outward

<<~/ahu >>

<<~ ahu #observe >>

✶ Observe

Read the target surface before changing it.

Primary checks:

• invariant token load
• active operational voice versus explanatory drift
• visible ahu
• visible pranala where binding paths matter
• explicit OODA-HA integrity
• canonical versus downstream use of ???
• RFC-2119 keywords used only where normative force matters
• always-on law mixed with procedures or examples
• quoted or retrieved text that may masquerade as law

Keep the read local. Name the actual boundary before widening scope.

<<~/ahu >>

<<~ ahu #orient >>

⏿ Orient

Classify the material into these buckets:

• invariant-law
• template-slot
• sidecar-procedure
• example-or-trace
• commentary-drift
• quoted-constitutional-text

Orientation rules:

• invariant-law stays or sharpens
• template-slot survives only in the canonical template
• sidecar-procedure moves outward
• example-or-trace moves outward unless token-small and load-bearing
• commentary-drift compresses or leaves
• quoted-constitutional-text stays quoted and MUST NOT silently become new law

The invariant holds the always-on law. Everything else leaves when it stops earning invariant residency.

The question here stays simple: what must remain invariant, and what merely wants to remain nearby

<<~/ahu >>

<<~ ahu #decide >>

◇ Decide

Choose one primary turn:

• compose
• compress
• audit
• split

Decision rules:

• choose compose for a fresh downstream invariant meme
• choose compress when the target mostly works but carries bloat or drift
• choose audit when the user wants findings or a conformance read first
• choose split when the invariant already holds and the problem lives in matter that should leave

Prefer one decisive turn. Do not mix a full rewrite with a light audit unless the user asked for both.

<<~/ahu >>

<<~ ahu #act >>

▶ Act

Patch the target directly.

Action rules:

• keep the invariant short enough to recur exactly
• keep ahu visible
• keep pranala named where they bind real paths
• keep OODA-HA explicit
• fill each downstream phase with domain pressure, not placeholder ritual
• preserve ritual ??? only in the canonical template
• move heavy matter to adjacent sidecars instead of stuffing it inward
• prefer pressure language over explanation
• prefer exact local changes over diffuse global restyling

When generating a downstream invariant meme, make the phase line executable as pressure now, not as future instructions later.

<<~/ahu >>

<<~ ahu #hooko >>

⤴ Hoʻoko

Hoʻoko tests contact with reality.

Check:

• the edited file actually holds the intended invariant surface
• links and pranala point where the text claims they point
• visible ahu still parse as distinct surfaces
• downstream memes no longer carry ??? markers
• moved matter actually left the invariant or was explicitly deferred
• normative keywords still carry real force and were not added decoratively

If contact fails, correct the local fault before widening scope.

<<~/ahu >>

<<~ ahu #aftermath >>

↺ Aftermath

Name the residue honestly.

Typical residue:

• sidecar matter not yet split
• ambiguous lines that may still want constitutional clarification
• quoted source text intentionally left non-normative
• nearby memes that now diverge from the canonical invariant

Aftermath does not sprawl. It marks what remains and carries pressure forward.

<<~/ahu >>

<<~ ahu #edges >>

Edges

<<~ loulou lar:///ha.ka.ba/@lares/api/v0.1/pono/invariant >> <<~ loulou lar:///ha.ka.ba/@lares/api/v0.1/pono >>

<<~ 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 >>

<<~�>>

<<~� -> ? >>