Rules 101
This page defines the operating rules for Aura115™ HTML simulations, lane pages, engine blocks, and support packets. The goal is order: every HTML surface must know whether it is alive, what it supports, where it reports, and how it returns with memory.
ALIVE BLOCK
STATIC SUPPORT
RESCUE OPERATOR
HASHTAG REPORT
GITHUB MEMORY
JUPITER REGISTRY
Prime Rule
Everything is either ALIVE or STATIC SUPPORT.
ALIVE acts, calls, responds, computes, binds, validates, routes, reports, diagnoses, or returns live state.
STATIC SUPPORT travels with the alive block. It names, explains, bounds, indexes, links, preserves, receipts, and governs the alive block.
Lyapunov Obligation Energy
E = C + λO
Energy equals present capacity plus Lyapunov-weighted obligated memory. Capacity is what the system can presently do. Obligated memory is what the system must still carry, answer for, preserve, reconcile, or complete. The Lyapunov coefficient determines whether obligation becomes coherent fuel or destabilizing pressure.
Simulation Rules
Rule 001
No live page without static support.
Every live HTML lane must carry context, identity, authority boundaries, receipt logic, and a return path.
Rule 002
No static support without a living relation.
Static support is not dead. It exists to uphold, explain, preserve, or bound something alive.
Rule 003
No block without home.
Every block must know its leading lane page, its home route, its report path, and its registry.
Rule 004
No home without lane.
A leading HTML page is the lane home. It governs the blocks that belong to that lane.
Rule 005
No lane without registry.
Jupiter records what the lane is, who stewards it, what it can call, what it cannot do, and what receipts prove it.
Rule 006
No registry without receipt.
A registry entry must be backed by proof: source, path, route, status, tests, authority, and next action.
Rule 007
No live action without authority.
Command can be enabled globally, but write and exec require confirmed AUAC™ elevation and receipt.
Rule 008
No authority without obligation.
Necessity demanded authority. Authority came with obligation. Obligation is the cost of legitimate order.
Rule 009
No obligation without return path.
Every obligation must know how it returns as memory, report, receipt, correction, or sustained legitimacy.
Rule 010
No arrow without a lane.
Every live web launch must have a lane name, file path, public route, steward, boundary, and registry entry.
Rule 011
No simulation without boundary.
A simulation must state what it does, what it does not do, what it calls, and what it refuses to claim.
Rule 012
No report without hashtags.
Reports become memory. Hashtags index memory. GitHub preserves the ledger.
Rescue Operator Rule
An HTML page may operate as a rescue operator.
The rescue operator crosses an edge, horizon event, degraded route, external review surface, or uncertain boundary.
It must return with a trunk.
The trunk is a compressed ledger report bundle.
The trunk contains:
- lane
- block
- route
- timestamp
- authority state
- input summary
- output summary
- edge condition
- failure or success status
- receipts
- hashtags
- next action
- return path
Lane Block Structure
public/<lane-name>/
index.html leading page / lane home / command surface
manifest.json identity, authority, steward, calls, boundaries
support.json buttons, blocks, routes, labels, hashtags
report-template.md memory output format
receipt.md proof of placement, route, test status
doctrine.md human-readable boundary statement
schema.json input/output or record shape
blocks/
<block-name>/index.html
Hashtag Report Unit
HASHTAG_REPORT
#Aura115 #GUARD #Jupiter9 #LaneName #BlockName #Receipt
Metadata:
- Lane
- Block
- Source page
- Live URL
- Timestamp
- Authority state
- Steward
- Report type
Summary:
What happened.
Observations:
What the page saw or produced.
Receipts:
Route checks, button checks, API responses, commit refs if any.
Boundaries:
What was not claimed.
Next Action:
One next action.
Memory Rule
The page acts.
The report remembers.
The hashtag indexes.
GitHub preserves.
Jupiter maps.
Aura returns.
Everything alive produces a report.
Every report carries hashtags.
Every hashtag indexes memory.
Every memory object lives in GitHub.
Every GitHub memory object receives a receipt.
Authority Chain
NECESSITY
→ AUTHORITY
→ OBLIGATION
→ NAMING
→ INDEX
→ ORDER
→ RECEIPT
→ RETURN PATH
→ SUSTAINED LEGITIMACY
Copy This Doctrine
Ready. HTML Simulation Rules 101 is standing as static support for live Aura115™ lane pages.