Skip to content

CANON.md

Latest commit

 

History

History
38 lines (31 loc) · 2.46 KB

CANON.md

File metadata and controls

38 lines (31 loc) · 2.46 KB
Raw

SillPak canon

Status: Ratified public product boundary, 2026-07-16

SillPak is a local-first routed artifact workspace where artifacts become pages and terminal and browser sessions persist as tools. It may supervise bounded physical operations, but it does not own semantic intent, orchestration, durable truth, or external policy.

SillPak works independently and exposes optional adapters for external context, control, execution, and evidence systems.

Ownership

  • Astro owns route identity, browser history, route data, and artifact-page replacement.
  • LiteShip owns adaptive shell projection, capability-aware layout, CSS and ARIA agreement, live non-route regions, and opaque specialist boundaries.
  • Authenticated local HTTP owns routed artifact reads, projections, and bounded saves.
  • Electron IPC owns terminal control, workspace selection, native file actions, and future browser-session control.
  • Specialist engines own their internal rendering surfaces.
  • External systems may attach through narrow adapters, but their semantics do not enter SillPak's public contracts.

Product laws

  1. The artifact route remains the artifact identity.
  2. Filesystem navigation is concrete; no generic provider graph exists before a second backend earns it.
  3. Interactive terminal sessions and bounded process attempts are different contracts.
  4. Interactive browser sessions and bounded browser actions are different contracts.
  5. Enforcement and observation are separate axes.
  6. A watcher may associate changes with a time window; it may not claim causality.
  7. Unsupported required constraints fail before a bounded attempt starts.
  8. Renderer loss detaches from a running terminal; it does not terminate it.
  9. Remote web content receives no native bridge, terminal authority, or local session credential.
  10. The public repository contains no private stack hierarchy or product semantics.
  11. A browser action may target an attached session or an ephemeral worker.
  12. WebMCP is a page-authored action source, not authority.
  13. Page-tool hints cannot grant profile access, broaden origins, or skip confirmation.
  14. Accessibility remains a first-class action and inspection surface.
  15. Page-tool and accessibility references are generation-bound and fail stale.
  16. A logged-in browser profile does not authorize agent control.
  17. Downloads enter holding before workspace promotion.
  18. Uploads require artifact grants.
  19. One browser action produces one physical attempt and one report.