Wardline Framework Specification¶
The normative reference for all wardline language bindings.
Part I — Language-Independent Framework¶
The core specification defines the authority tier model, enforcement rules, governance, and conformance requirements that all language bindings must implement.
§ 1 Document Scope — What the specification covers and its intended audience
§ 2 What a Wardline Is — Core concept: a declared trust boundary in code
§ 3 The Problem a Wardline Solves — Untrusted data reaching privileged code without validation
§ 4 Non-Goals — What wardline intentionally does not address
§ 5 Authority Tier Model — The four-tier trust hierarchy and taint classification
§ 6 Authority Tier Enforcement — Taint joins, restoration evidence, and tier transition rules
§ 7 Annotation Vocabulary — Decorators and annotations that mark trust boundaries
§ 8 Pattern Rules — WL-001 through WL-009: the detection rule catalogue
§ 9 Enforcement Layers — Static, type-system, runtime, and structural enforcement
§ 10 Governance Model — Exception register, control-law state machine, retention
§ 11 Verification Properties — Golden corpus, formal properties, testing requirements
§ 12 Language Evaluation Criteria — Criteria for adding new language bindings
§ 13 Residual Risks — Known limitations and compensating controls
§ 14 Portability & Manifest Format — wardline.yaml schema, overlays, and cross-platform format
§ 15 Conformance — Obligation-ledger conformance, profiles, and release projections
Part II — Language Bindings¶
Language-specific implementation contracts. Each binding maps the abstract framework to concrete language constructs.
§ A Python Language Binding — Decorators, regime composition, error handling, adoption
§ B Java Language Binding — Annotations, record types, module system, Checker Framework