loci

name	loci
description	Perform, audit, or repair a loci routing-and-rating pass under lar:///ha.ka.ba/@lares/api/v0.1/pono/loci. Use this skill for URI intake, derivation algorithm execution, resolution posture commitment, canon-promotion evaluation, file-path migration, or routing aftermath judgment.
allowed-tools	Read, Grep, Glob, Bash, Edit, Write

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

uri-path = "ha.ka.ba/@lares/api/v0.1/pono/loci/SKILL"
file-path = "bags/@lares/api/v0.1/pono/loci/SKILL.md"
type = "text/x-memetic-wikitext"
confidence = 0.70
register = "CS"
manaoio = 0.64
mana = 0.72
manao = 0.80
role = "agent-facing procedural surface for loci routing and rating passes"
covers = ["lar:///ha.ka.ba/@lares/api/v0.1/pono/loci"]
constraints = [
  "S1: the canonical loci remains the stable-address interface law",
  "S2: derivation algorithm runs in full step order without skipping",
  "S3: resolved and declared-unresolved stay distinct; neither collapses into the other",
  "S4: rating commitment stays truthful; a path hit never overrides honest unresolved tension",
  "S5: file-siting mutations and opener changes cross as distinct bounded Hoʻoko transactions",
  "S6: aftermath names all declared-unresolved addresses; none silently disappear"
]
skill-package-root = "packages/lares-core/memes/api/v0.1/pono/loci"

Loci / SKILL

Read loci.md first. Treat that loci as constitutional. This skill runs that law through the OODA-HA cycle. This skill does not widen, soften, or reinterpret it.

<<�>> Loci SKILL opens the procedural stream here. <</ahu >>

<<~�>>

<<~ ahu #load-contract >>

Load Contract

• loci.md stays the constitutional source
• derivation algorithm runs in full step order; never skip
• resolved and declared-unresolved stay distinct; declared-unresolved carries real forward pressure
• rating commitment stays truthful; a path hit never overrides unresolved tension
• file-siting mutations and canon-promotion opener changes cross as distinct bounded Hoʻoko transactions
• aftermath names all declared-unresolved addresses
• stable tagspace: lar:///ha.ka.ba/@lares/ → packages/lares-core/memes/; all other \w\.\w\.\w roots → lares/chapel-perilous-opens/{root}/
• loci eligibility requires \w\.\w\.\w root path segment; outside that pattern, MAY NOT implement
• MCP resolution remains research backlog; no live resolver operates today

<<~/ahu >>

<<~ ahu #workflow-contract >>

Workflow Contract

Four main paths:

1. fresh routing-and-rating pass on a lar: URI
2. audit an existing carrier for loci convention compliance
3. cross a file-siting migration as a bounded Hoʻoko transaction
4. evaluate a carrier for canon-promotion readiness

Workflow:

1. load the canonical loci
2. identify the request: URI to resolve, migration to cross, or carrier to audit
3. run the derivation algorithm in full step order
4. classify resolution state; read convention surfaces
5. commit to resolution posture, rating posture, canon-lifecycle stage
6. prepare the routing product
7. cross any file-siting or opener change as a named Hoʻoko transaction
8. emit aftermath with all declared-unresolved addresses named

Do not:

• skip derivation steps
• collapse declared-unresolved into a near-match
• overrate a carrier to hide unresolved tension
• batch a file-siting mutation with a canon-promotion opener change silently
• claim MCP resolution operates when it does not

<<~/ahu >>

<<~ ahu #trigger >>

Trigger

Activate when the task concerns:

• resolving a lar: URI against the derivation algorithm
• auditing a carrier's file-path against the stable file-path convention
• evaluating canon-promotion readiness
• crossing a file-siting migration or repair as a Hoʻoko transaction
• assigning or reviewing mana, manao, manaoio for a loci-typed carrier

Not for:

• MCP server design or live-resolver research → lar:///ha.ka.ba/@lares/api/v0.1/pono/loci/iam
• generic meme law → lar:///ha.ka.ba/@lares/api/v0.1/pono/meme
• invariant compression or sidecar splitting → lar:///ha.ka.ba/@lares/api/v0.1/pono/invariant/SKILL

<<~/ahu >>

<<~ ahu #ooda-ha >>

✶ begin from canonical loci; gather URI and convention surfaces before decomposition ⏿ run the derivation algorithm in full step order; classify resolution state without collapse ◇ commit to one resolution posture and one rating posture; keep resolved and declared-unresolved distinct ▶ prepare the routing product and cross mutations as bounded Hoʻoko transactions ⤴ verify ratings stay truthful under unresolved tension and transaction bounds stayed explicit ↺ name aftermath including all residue and all declared-unresolved addresses

<<~/ahu >>

<<~ ahu #observe >>

✶ Observe

Read the target before any decomposition.

• the full lar: URI string, verbatim
• known meme-type, prior rating posture, or prior promotion context if present
• document opener form: <<~&#x0001; ? -> ... (unbound) or <<~&#x0001; lar:///... (confirmed canon)
• visible convention surfaces: #iam, register, file-path, promotion note
• first-pass or re-resolution of a previously declared-unresolved address
• calling context: mid-parse urgency differs from session-load intake

Do not decompose the URI here. Do not fabricate a resolution substrate. Do not infer implements loci without evidence.

<<~/ahu >>

<<~ ahu #orient >>

⏿ Orient

Decompose; classify resolution state.

• step 1: match ^lar:\/\/[^\/]*\/(\w+\.\w+\.\w+)\/(.+)$; extract root and sub-path; if no match, carrier ineligible — emit and stop; authority may be empty (lar:///) or full (lar://alias:tier@host/)
• step 2: if root == "ha.ka.ba" → packages/lares-core/memes/ + stem + .md; else → lares/chapel-perilous-opens/ + root + / + stem + .md
• step 3: file exists → RESOLVED; file absent → DECLARED-UNRESOLVED; emit forward reference
• read convention surfaces against the derivation result
• hold RESOLVED and DECLARED-UNRESOLVED as distinct throughout

A lar: URI in a depends-on array that resolves to no derived path counts as declared-unresolved — real constraint on promotion and rating.

<<~/ahu >>

<<~ ahu #decide >>

◇ Decide

Commit to one resolution posture, one rating posture, one canon-lifecycle stage.

• prefer derived-path resolution when the candidate file exists
• derivation miss → name declared-unresolved directly; do not soften to "near match"
• lower readiness for declared-unresolved; do not pretend a missing resolver resolves
• canon-lifecycle: a carrier may not self-promote; all conditions in lar:///ha.ka.ba/@lares/api/v0.1/pono/loci/iam MUST hold

Rating posture:

• mana rises: clean derivation, explicit convention surfaces, honest miss naming
• manao rises: carrier knows its loci role; enacted law stays separate from roadmap speculation
• manaoio rises: resolution repeats reliably; backlog surfaces honestly

<<~/ahu >>

<<~ ahu #act >>

▶ Act

Prepare the routing product.

Product forms:

• rating set (mana, manao, manaoio, register)
• resolved carrier filepath string
• declared-unresolved forward reference with full lar: URI and classification
• canon-promotion readiness verdict
• Hoʻoko transaction envelope for file-siting mutations

Do not:

• invent a local registry to cover unresolved tension
• emit a roadmap note as if a live resolver operates
• batch a file-siting mutation with a canon-promotion change in one unlabeled step

<<~/ahu >>

<<~ ahu #hooko >>

⤴ Hoʻoko

Cross where routing state changes.

Each transaction MUST name: lar-uri, the change made, and the authorizing agent or operator. File-siting mutation and canon-promotion opener change MUST NOT batch silently.

Before crossing:

• target lar: URI stays unchanged
• parent meme stays at its derived filepath
• child items stay under the sibling terminal-segment directory
• canon promotion: all address-stability conditions hold; ? removal only after operator confirmation

Migration history:

• ha-ka-ba/api/v0.1/pono/loci/loci.md → ha-ka-ba/api/v0.1/pono/loci.md
• ha-ka-ba/api/v0.1/pono/loci/iam/loci-iam.md → ha-ka-ba/api/v0.1/pono/loci/iam.md

In each case the lar: address held stable; file siting returned to the derived position.

<<~/ahu >>

<<~ ahu #aftermath >>

↺ Aftermath

Name what resolved, what ratings hold, and what remains open.

One completeness judgment per routing pass:

• which URIs resolved via derivation
• which URIs remain declared-unresolved
• what mana, manao, manaoio posture holds
• whether explicit convention still holds across all surfaces
• what closes each declared-unresolved address
• whether remaining tension reads as authoring backlog or MCP-resolution research

After one address resolves, widen: does the stack describe itself coherently after recent migrations?

Aftermath that names only resolved URIs hides the pressure that matters most.

<<~/ahu >>

<<~ ahu #edges >>

Edges

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

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

<<~�>>

<<~� -> ? >>