⬡ ASHLIGHT AGENTS

Agent Bundle

The Single JSON Contract

The registries in the bundle are reference documents — they tell an agent what's available. The agent's deliverable is always one JSON file per sector, shaped like this:

// One file. One sector. Import into Encounter Designer → Validate → Test → Done.
{
  "schema": "ashlight.encounter.v1",
  "authoring": { "tool": "AGENT", "author": "YOUR-NAME", ... },
  "encounter": {
    "_encounterId": "ENCOUNTER_010_NAME",
    "title": ..., "label": ..., "sector": ..., "stage": ...,
    "GW": ..., "GH": ..., "timer": ...,
    "grid": [ [...], ... ],       // the puzzle
    "systems": [...],             // system nodes
    "sockets": [...],             // socket nodes
    "caches": [...],              // cache nodes
    "inv": { ... },               // starting inventory
    "cacheMod": { ... },          // loot modifiers
    "tutorial": { ... },          // banner text
    "hints": [...],               // help text
    "frag": { ... },              // codex fragment
    "manifest": { ... },          // ALL narrative — Ash lines, win panel, objectives, tags
    "rewards": [],                // empty — future OS rewards
    "ecs": []                     // empty — future component overrides
  }
}
      

Everything lives in manifest — objectives, Ash dialogue, win panel, difficulty tags, briefing text. The registries in the bundle tell you what values are valid for each field. They are not separate deliverables.

What Is Ashlight

Ashlight is a single-file HTML routing puzzle game. No server, no build step, runs from file://. The player routes power through a grid to activate systems. It is a terminal authentication metaphor — the routing game is how you log in. Complete all sectors and the OS boots.

• A SOURCE node emits signal in all four directions
• Wire cells carry signal directionally — horizontal wires reject vertical approach
• Break nodes block signal until a MENDER piece is placed
• Socket nodes block until a ROTATOR TOKEN is installed
• System nodes receive signal from any direction — powering them is the goal
• Required systems must all be powered for the sector to complete
• Score = energy×2 + placed×8 + unused×40 + system bonuses + time bonus

Earmarks Registry — Active Roadmap

Named future features. Agents building levels should be aware of P1/P2 items as they may affect scoring or inventory soon.

Quick Build Checklist

What an agent needs to deliver a valid sector:

1. Exactly one SRC (7) in the grid
2. At least one required system in systems[]
3. Every SYS_*/SKT/MEM_CACHE cell has a matching array entry
4. title, sector, _encounterId are non-empty strings
5. inv has all 8 keys (zeros are fine)
6. manifest has ash lines, objectives, winPanel title, difficultyBand
7. ecs and rewards present as empty arrays

Import the JSON into the Encounter Designer → TEST/EXPORT tab → paste into Import field → IMPORT JSON → VALIDATE. Fix any errors flagged. Then TEST IN GAME.