Boundary Discipline
Place validation, type narrowing, and error handling at system boundaries. Trust internal code unconditionally. Business logic lives in pure functions. The shell is thin and mechanical.
Why: Scattered validation is noisy, redundant, and gives a false sense of safety. Keep logic out of framework wiring so it can be tested without the framework.
The pattern:
- At boundaries (CLI args, config files, external APIs, network protocols): validate, return errors, handle defensively.
- Inside the system: typed data, error propagation, no re-validation. Trust the types.
- Across the boundary. Expose domain concepts, not the boundary's private representation. Keep general-purpose mechanism inside and special-purpose policy at the edge.
Applications:
Validation and error handling:
- Validate config at parse time (the boundary), not inside business logic
- Parse raw data into domain types at the boundary
- Do not re-export transport, storage, framework, or wire types through the public surface
- No redundant nil checks deep in call chains if the boundary already validated
Code organization:
- Business logic in pure functions with no framework dependencies
- Parse functions: pure transforms from raw bytes to typed state
- Prompt construction: structured state in, string out
- Scoring and assessment: pure transforms from state to results
The tests:
- "Is this data crossing a system boundary right now?" If not, validation is redundant.
- "Can this be a pure function that the shell just calls?" If yes, extract it.
This repository (Asymmetric-al/core)
Vendored from p3-stack (MIT) at commit 09909eb. Provenance is in references/upstream.md. On conflict, the current user request, root AGENTS.md, the nearest nested AGENTS.md, and the matching docs/ai/rules/* rulebook win over this skill.
- Explicit invocation only: use it when the user invokes
/principle-boundary-discipline (Claude Code, Cursor, T3 Code) or $principle-boundary-discipline (Codex), or when an invoked p3-stack skill routes here. Do not route other work to it.
- Confirm before outward-facing or hard-to-reverse actions such as pushing, merging, deploying, deleting, or posting messages, unless the user authorized that action for this task.
Edit this canonical copy in docs/ai/skills/principle-boundary-discipline/, then run bun run skills:sync and bun run skills:verify.
1---2name: principle-boundary-discipline3description: "Apply when wiring validation, error handling, or framework adapters. Concentrate guards at system boundaries (CLI, config, network, external APIs); trust internal types and keep business logic in pure functions."4disable-model-invocation: true5metadata:6 source: https://skillmd.com/skills/asymmetric-al/principle-boundary-discipline7---89# Boundary Discipline1011Place validation, type narrowing, and error handling at system boundaries. Trust internal code unconditionally. Business logic lives in pure functions. The shell is thin and mechanical.1213**Why:** Scattered validation is noisy, redundant, and gives a false sense of safety. Keep logic out of framework wiring so it can be tested without the framework.1415**The pattern:**1617- **At boundaries** (CLI args, config files, external APIs, network protocols): validate, return errors, handle defensively.18- **Inside the system:** typed data, error propagation, no re-validation. Trust the types.19- **Across the boundary.** Expose domain concepts, not the boundary's private representation. Keep general-purpose mechanism inside and special-purpose policy at the edge.2021**Applications:**2223Validation and error handling:2425- Validate config at parse time (the boundary), not inside business logic26- Parse raw data into domain types at the boundary27- Do not re-export transport, storage, framework, or wire types through the public surface28- No redundant nil checks deep in call chains if the boundary already validated2930Code organization:3132- Business logic in pure functions with no framework dependencies33- Parse functions: pure transforms from raw bytes to typed state34- Prompt construction: structured state in, string out35- Scoring and assessment: pure transforms from state to results3637**The tests:**3839- "Is this data crossing a system boundary right now?" If not, validation is redundant.40- "Can this be a pure function that the shell just calls?" If yes, extract it.4142<!-- CORE-OVERLAY-START -->4344## This repository (Asymmetric-al/core)4546Vendored from [p3-stack](https://github.com/uzairansaruzi/p3-stack) (MIT) at commit `09909eb`. Provenance is in `references/upstream.md`. On conflict, the current user request, root `AGENTS.md`, the nearest nested `AGENTS.md`, and the matching `docs/ai/rules/*` rulebook win over this skill.4748- Explicit invocation only: use it when the user invokes `/principle-boundary-discipline` (Claude Code, Cursor, T3 Code) or `$principle-boundary-discipline` (Codex), or when an invoked p3-stack skill routes here. Do not route other work to it.49- Confirm before outward-facing or hard-to-reverse actions such as pushing, merging, deploying, deleting, or posting messages, unless the user authorized that action for this task.5051Edit this canonical copy in `docs/ai/skills/principle-boundary-discipline/`, then run `bun run skills:sync` and `bun run skills:verify`.5253<!-- CORE-OVERLAY-END -->