An entry is a defined point of access to a system. It specifies who or what may enter, through which interface, under which contract.
Definition
An entry declares a boundary: a typed interface with an explicit contract and validation. It is the gateway, not the implementation behind it.
Purpose
- Make every access point explicit and validated.
- Separate the interface from what runs behind it.
- Give each context one predictable way in.
Principles
explicit— every entry is declared, never accidental.typed— user, system, data, or event; each carries its own contract.validated— input is checked at the boundary, not after.resolvable— paths and access rules are deterministic.
Anti-patterns
- Undocumented or accidental entry points.
- Validation deferred past the boundary.
- One interface overloaded for unrelated contexts.
- Access that depends on caller knowledge.
Output Standard
Each entry declares its type, interface, contract, and validation — usable without reading the implementation.
Related
Validated by value, organized by layer, specified by std.
Contact
For architecture review or partnership, write to hi@entry.md.