Authority model / current note
Audit Authority as a Data Flow
A field method for mapping what a process can name, request, receive, and delegate.
Open field note ↗SYSTEMS / CAPABILITIES / PORTABILITY
Trust less.
Name every boundary.
Field notes for engineers who want authority, process state, runtime contracts, and portability assumptions to remain visible in system design.
Read the notes →
Current issue / six notes
Portable code starts with an explicit contract.
Historical address / new FreeBSD note
FreeBSD: Verify the Host Contract
An independent checklist for testing a constrained runtime boundary on a current FreeBSD host.
Open field note ↗Historical address / new Linux note
Linux: Make the Sandbox Layers Observable
An independent Linux test plan for namespaces, system-call limits, resource handles, and failure evidence.
Open field note ↗Historical address / new macOS note
macOS: Separate Build Portability From Runtime Authority
An independent method for documenting platform assumptions when a systems workload is built or tested on macOS.
Open field note ↗Historical address / new Rust note
Rust: Encode the Boundary, Then Test the Unsafe Edge
An independent Rust design note for capability handles, ownership, unsafe adapters, and operating-system errors.
Open field note ↗Portability / current note
Write the Portable Runtime Contract First
A checklist for separating portable workload behavior from host-specific adapters.
Open field note ↗The former domain documented the CloudABI open-source runtime. This publication preserves useful technical addresses without claiming that project, its code, or its maintainers.
Read the identity statement