A language model for protected capability execution.
AFACode is designed to express authority, capability, policy, and execution constraints without exposing the durable operational route needed to fulfil them.
Public design goals
Capability-first
Code requests governed capability instead of embedding permanent service locations.
Authority-native
Execution depends on evaluated authority, not application-owned reusable credentials.
Opaque artefacts
Compiled outputs prioritise commitments and constraints over operational disclosure.
AFACode and security language design
AFACode positions protected software around policy, capability and execution posture rather than static infrastructure references. It supports the public AFA objective: reduce the operational value of stolen code, binaries and deployment artefacts.
Information boundary
The public AFACode description is intentionally limited to security objectives and taxonomy. Grammar, compilation mechanics, provider bindings, and runtime orchestration remain proprietary.