plaited-runtime

plaited-runtime

Purpose

Use this skill as the compact doctrine for current Plaited runtime work: behavioral coordination, MSS/module boundaries, projection semantics, and module actor boundaries.

Before Coding Or Reviewing

Run plaited-context first for source-grounded context assembly:

bun skills/plaited-context/scripts/context.ts '{"task":"<task>","mode":"review","paths":["<paths>"]}'

For module actor work, run deterministic pattern and flow evidence:

bun skills/plaited-context/scripts/module-patterns.ts '{"files":["<module-files>"]}'
bun skills/plaited-context/scripts/module-flow.ts '{"files":["<module-files>"],"format":"json"}'
bun skills/plaited-context/scripts/module-flow.ts '{"files":["<module-files>"],"format":"mermaid"}'

Use "record": true only when a plaited-context DB has already been initialized or a dbPath is provided for the review run.

Behavioral Runtime Rules

• Behavioral programming is the deterministic runtime coordination substrate.
• Use behavioral(), bThread, bSync, useFeedback, and useSnapshot.
• Do not write raw generators/yields in repo behavioral code.
• Threads coordinate timing and constraints; handlers perform side effects.
• Blocks are observable in snapshots and do not queue blocked events.
• Add dynamic threads before triggering events they must observe.
• Use detailMatch: 'invalid' when blocking malformed payloads.

Module / MSS Rules

• MSS defines what may be projected.
• Target descriptive MSS vocabulary is content, structure, mechanics, and boundary; legacy scale is compatibility metadata until schemas are migrated.
• Runtime or supervisor decides whether projection is allowed.
• Protocol adapters expose approved projections.
• Protocols are mechanics, not ontology.
• Preserve source/provenance; do not rewrite source to fake approval.
• Auth/session/token mechanics are not modnet ontology.
• UI is a local projection. Cross-node interoperability is facts/resources, services/actions, policy/grants, provenance, and approved projections.

Projection Rules

• Treat projection policy as runtime-governed semantics, not transport default.
• Expose only approved projections through adapters and module boundaries.
• Keep trust/authority assumptions explicit in runtime policy.

Module Actor Boundary Rules

• Core modules under src/modules are flat single TypeScript files.
• src/modules/*.ts files are core runtime module actors, not user-facing module programs.
• User/developer-authored proposals should be called module programs until admitted by runtime policy.
• Do not create nested module implementation folders under src/modules.
• src/modules.ts remains the public modules boundary.
• Audience-specific projection views are governed projections, not independent source modules unless they own separate state/provenance.
• Declared access requests in module descriptors are asks, not grants.
• Skill/CLI/inference/external-service declarations are review metadata until a later grant policy path allows them.
• External boundary ingress should parse with .parse(...) inside try/catch and publish diagnostics/snapshots.
• Internal useExtension(...) feedback/control handlers parse strictly and should not catch ZodError locally.
• Actor/runtime failures use reportSnapshot(...), not transport diagnostics or synthetic diagnostic events unless there is a real protocol consumer.

Diagnostics And Parsing Rules

• External transports may emit transport diagnostics for malformed ingress.
• Internal actor/control parsing failures should surface as feedback_error/extension_error snapshot diagnostics.
• Prefer strict .parse(...) in runtime handlers over local safeParse silent-drop patterns.

What Not To Assume

Other than the two-model inference direction and current source-backed inference websocket runtime actor/server, docs and skills are not authoritative when they mention event names, module names, actor APIs, server surfaces, or runtime contracts that do not exist in current src/ code or tests.

Do not promote doc-only names into doctrine unless they exist in source/tests or are required by an external spec.

Treat docs/wiki/infrastructure.md as deployment target material, not implemented runtime doctrine. Treat docs/wiki/local-inference-bridge.md as the target local inference bridge decision; current source still includes the WebSocket inference runtime actor.

References

• references/behavioral-runtime.md
• references/modnet-mss-lineage.md
• references/module-actor-boundaries.md
• references/agent-runtime-notes.md

Related Skills

• plaited-context
• mss-module-review
• typescript-lsp
• plaited-development