한국어 | English
Core Spec Index | Protocol Index | Systems Index
ZLink public specification¶
This directory defines the ZLink public API contract. Its audience is Core and bindings implementers and public-contract reviewers. Formal documents linked from this index are authoritative for function signatures, returns, errors, ownership, and thread safety.
1. Document structure¶
| Area | Document | Description |
|---|---|---|
| Core C ABI | Core specification | C functions, types, enums, and runtime behavior |
| Bindings | Bindings specification | Language-specific public projections of the Core contract |
Formal specifications describe only the current contract. Guides own purpose and examples, while internals own actual internal structure after implementation is complete. Contract reviewers navigate from this index and the public header.
2. Main Core documents¶
| Document | Public contract |
|---|---|
| Contract governance | Consistency among specification, headers, tests, and packages |
| Context | Context lifecycle and options |
| Message | Message and routing-ID storage and ownership |
| Socket | Generic socket types and send/receive behavior |
| Polling | Poll items, pollers, and readiness |
| Monitoring | Raw-socket monitors and snapshots |
| Runtime boundary | Core raw C ABI and Framework service responsibility boundary |
| Events | Public events and state-transition meaning |
| Errors | Result enums, errno, and the version ABI |
| Errno map | Per-function result and errno mappings |
| Utilities | Timers, threads, stopwatch, and atomic utilities |
3. Conformance¶
A conforming implementation provides every function, type, constant, and behavior in the formal documents. A mismatch among public headers, exported symbols, contract tests, bindings, installed packages, and the formal specification is nonconforming. Internal implementation details are not exposed as public contracts, and a language-specific API cannot reduce the shared contract.