Who or what is asking—and for what purpose
- Principal + workload identity
- Device + environment attestation
- Purpose + resource scope
- Risk + geography + obligations
- Eligible immutable model release
- Human or multi-party approval when policy requires
01 // SYSTEM BRIEF // DESIGN BASELINE // 2026
Governed authority for AI working with sensitive data and real systems.
FortEmerald is a design-stage control plane for minimum useful context, bounded authority, deterministic execution, and tamper-evident, privacy-aware evidence.
MODE vendor-neutral by design
POSTURE deny by default
CRYPTO agile · PQ-ready path
STAGE architecture · no production claim
01SENSITIVE DATAclassified · minimized · compartmented
[
FORTEMERALDidentity + context + authority + evidence
]02AI + AGENTSexternal · confidential · sovereign
03TOOLS + MACHINESbounded intent · local safety · observed result
02 // SYSTEM DEFINITION
One control plane between a request and its consequences.
FortEmerald is designed to coordinate authority, context, execution, and evidence across systems that already own identity, data, models, tools, infrastructure, and devices.
What may cross—and what may execute
- Purpose-bound, expiring context capsule
- Opaque references resolved outside the model
- Untrusted model proposal
- Single-use or short-lived capability
- Deterministic connector + local safety
- Disclosure, decision, action, and outcome evidence
PEOPLE + AGENTS↔DATA↔MODELS↔TOOLS + APPS↔MACHINES//ONE GOVERNED CONTRACT
03 // THE CONTROL GAP
AI is moving from producing information to requesting authority.
The risk changes as systems progress from answering, to deciding, to calling tools, to directing software and physical operations.
Private context enters inference
- Raw records and broad prompts
- Variable retention and training terms
- Purpose boundaries disappear
Output influences judgment
- Probabilistic recommendations
- Hidden lineage and model drift
- Unclear accountability
Agents call real systems
- Reusable credentials
- Delegated tool chains
- Expanded blast radius
Intent reaches machines
- Intermittent connectivity
- Slow revocation at the edge
- Safety cannot depend on a model
ANSWER→RECOMMEND→DELEGATE→ACT→CONTROL=AUTHORITY MUST BECOME EXPLICIT
04 // THE PROBLEM
The central problem is fragmented authority.
Identity, data access, model routing, secrets, approvals, actions, and audit often travel through different provider-specific paths.
Too much context
Models receive complete records when a scoped fact, class, range, or opaque reference would be enough.
Ambient power
Long-lived credentials make an agent’s practical authority broader than the task being performed.
Proposal becomes action
Probabilistic output can flow into tools without a separate policy decision and deterministic boundary.
Broken lineage
No single record joins identity, purpose, disclosure, model release, decision, action, and observed result.
WHY NOW: Every new model, agent framework, data source, tool, cloud, and device adds another control path unless authority is normalized above them.
05 // SIX CONTROL OUTCOMES
A unified answer to six separate questions.
Know
Verified human, workload, model, device, and environment identity.
Limit
Policy evaluates purpose, classification, geography, risk, and obligations.
Contain
Minimum useful, scoped, temporary, expiring context—not the source record.
Bound
Short-lived capability restricts audience, action, resource, time, and delegation.
Execute
Deterministic connectors validate proposals and local controllers retain safety.
Prove
Tamper-evident, privacy-aware evidence records governed transitions and outcomes.
>_
OPERATING PRINCIPLE // Models may propose. FortEmerald decides what they may receive and what can execute.
06 // GOVERNED ROUTE
From purpose to evidence—without turning a model into the authority system.
Each boundary has one job. Model output remains untrusted until the next policy and execution boundary validates it.
01IDENTITYprincipal + workload
→
02POLICYdecision + obligations
→
03CAPSULEminimum useful context
→
04MODELeligible release
→
05PROPOSALuntrusted output
→
06CAPABILITYbounded authority
→
07EXECUTIONdeterministic connector
→
08EVIDENCEtransition + outcome
R-01Purpose firstNo context before a decision.
R-02Minimum useful contextScoped, temporary, expiring.
R-03Immutable model releaseEligibility is policy-derived.
R-04Conditional approvalHuman or multi-party when required.
R-05Bounded executionNo reusable ambient authority.
R-06Privacy-aware evidenceNo raw secrets in normal telemetry.
07 // CONTROL-DOMAIN CONSTELLATION
Thirteen ownership domains. One FortEmerald contract.
These are cooperating control domains—not an OSI-style packet stack. Arrows indicate dominant runtime relationships; Alloy, Platinum, Copper, and Amber are cross-cutting.
L9 · ALLOYcrypto-agility + keys + post-quantum transition across every domain
Silicon
admission
Agate
attestation
Sapphire
authorization
Emerald
data boundary
Opal
gateway
Onyx
capabilities
Titanium
execution
Lodestone
device control
Amber
provenance
L10 · PLATINUMgovernance + operations
L11 · COPPERadapters + interoperability
L12 · GARNETAI development + model lifecycle extension
MVP SCOPE L0–L6 · L8–L11LIFECYCLE EXTENSION L12LATER PLATFORM CEILING L7 edge + device intentSTATUS design architecture; layer names are the working material system
SILICON
FOUNDATION // COMPUTE + ENVIRONMENT
Silicon
Verify the place where governed work is allowed to begin.
MATERIAL LOGIC // Silicon is the literal substrate of modern computing. Here it represents the foundation FortEmerald admits and measures—not a requirement that every deployment use silicon hardware.
CONTROLSWorkload admission
Environment posture · resource class · tenant boundary · isolation profile · runtime integrity
RECEIVESAttested workload request
Signed manifest · classification · requested resources · execution profile · policy obligations
PRODUCESAdmission decision
Eligible environment set · constraints · native scheduler handoff · evidence hooks
EXAMPLE
A classified inference request is admitted only to an eligible isolated environment; Kubernetes, Slurm, cloud, or hardware managers still choose placement.
DOMINANT RELATIONSHIPS
Garnet manifest→Agate identity→Sapphire admission→Silicon environment→Amber evidence
AGATE
WHO // WHAT // WHERE
Agate
Build identity from multiple evidence bands, not a single login.
MATERIAL LOGIC // Agate’s visible bands record stages of formation. The metaphor is layered evidence—human, workload, model, device, and environment—not a claim that agate patterns are inherently unclonable.
CONTROLSPrincipal trust
Federated identity · workload identity · device identity · attestation · delegation chain
RECEIVESEvidence bundle
IdP assertions · certificates · runtime measurements · device posture · model release identity
PRODUCESCanonical principal
Normalized identity · assurance level · provenance · expiry · delegation limits
EXAMPLE
A service account, signed workload, and healthy device are joined into one expiring principal before policy evaluates access.
DOMINANT RELATIONSHIPS
External IdP + attestors→Agate→Sapphire→every governed route
SAPPHIRE
DECISION // OBLIGATION // APPROVAL
Sapphire
Turn identity and purpose into an explicit, reproducible decision.
MATERIAL LOGIC // Sapphire is exceptionally hard, durable, and optically clear. It represents a clear, durable boundary; selective authorization comes from policy logic, not from the stone itself.
CONTROLSPermission semantics
Purpose · classification · geography · risk · time · relationships · approval thresholds
RECEIVESCanonical request
Agate principal · resource attributes · device state · model eligibility · governance bundle
PRODUCESDecision contract
Permit or deny · obligations · context ceiling · capability limits · required approvals
EXAMPLE
Allow maintenance analysis for this role and region, redact location, route only to eligible releases, and require two-person approval before action.
DOMINANT RELATIONSHIPS
Agate→Sapphire→Emerald or Onyx→Amber
EMERALD
CLASSIFY // MINIMIZE // CAPSULATE
Emerald
Only the minimum useful context permitted for this purpose crosses.
MATERIAL LOGIC // Emerald is the valuable protected heart inside FortEmerald: sensitive context is shaped, compartmented, and guarded before it leaves its source boundary.
CONTROLSDisclosure boundary
Classification · minimization · redaction · tokenization · opaque references · retention
RECEIVESPermitted context ceiling
Sapphire decision · source schema · purpose · audience · expiry · disclosure policy
PRODUCESContext capsule
Audience-bound · scoped · temporary · expiring · source-attributed · receipted
EXAMPLE
An external model receives equipment condition and maintenance constraints—not unit, location, personnel, or the source record. If exact sensitive semantics are essential, policy routes to an approved confidential or sovereign model instead.
DOMINANT RELATIONSHIPS
Agate→Sapphire→Emerald capsule→Opal→Amber
OPAL
ROUTE // NORMALIZE // DISTRUST
Opal
One governed interface across external, confidential, and sovereign models.
MATERIAL LOGIC // Opal presents different color from different viewing angles because of its internal structure. It represents one controlled surface presenting the right approved view to varied model endpoints.
CONTROLSInference routing
Release allowlist · classification fit · geography · contract · risk · latency · cost
RECEIVESGoverned inference request
Expiring capsule · model constraints · immutable release identity · output schema
PRODUCESUntrusted proposal
Normalized response · release provenance · usage metadata · validation status · disclosure receipt
EXAMPLE
The same policy-controlled request can route to a commercial API, confidential-compute endpoint, or on-prem model without changing the authority contract.
DOMINANT RELATIONSHIPS
Emerald capsule→Opal eligible release→untrusted proposal→Sapphire / Onyx
ONYX
BROKER // BIND // EXPIRE
Onyx
Convert an approved decision into the smallest usable authority.
MATERIAL LOGIC // Onyx carries a familiar dark, bounded visual language for protected power. Natural onyx may be banded or translucent; the metaphor is containment, not a mineral claim of perfect opacity.
CONTROLSDelegated authority
Audience · action · resource · purpose · time · count · delegation · revocation
RECEIVESApproved action contract
Sapphire decision · required approvals · principal · target · execution obligations
PRODUCESBounded capability
Single-use or short-lived grant · opaque secret reference · proof-of-possession binding
EXAMPLE
An agent never receives a reusable drone or database credential; it receives authority for one permitted action against one target before expiry.
DOMINANT RELATIONSHIPS
Opal proposal + Agate→Sapphire→Onyx capability→Titanium / Lodestone
TITANIUM
VALIDATE // EXECUTE // OBSERVE
Titanium
Keep execution deterministic even when the proposal is probabilistic.
MATERIAL LOGIC // Titanium is valued for strength-to-weight and corrosion resistance, especially in engineered alloys. It represents durable execution with no more authority than the job requires—not “indestructible” action.
CONTROLSAction boundary
Schema validation · capability verification · idempotency · timeout · rollback · result state
RECEIVESProposal + capability
Untrusted structured proposal · bounded grant · target adapter · policy obligations
PRODUCESObserved outcome
Succeeded · failed · denied · timed out · indeterminate · reconciliation reference
EXAMPLE
A ticket update is schema-checked, capability-bound, executed once through a deterministic connector, then recorded with its observed result.
DOMINANT RELATIONSHIPS
Onyx capability→Titanium connector→external tool→Amber outcome
LODESTONE
DIRECT // VALIDATE LOCALLY // FAIL SAFE
Lodestone
Send bounded intent to the edge while local controllers retain safety.
MATERIAL LOGIC // Lodestone is naturally magnetized magnetite historically used for orientation and navigation. It represents bounded direction at the edge—not centralized pull or direct AI control of actuators.
CONTROLSMachine intent envelope
Mission scope · geofence · duration · rate · energy · connectivity · fail-safe mode
RECEIVESSigned bounded authority
Agate identity · Sapphire constraints · Onyx capability · trusted time · revocation state
PRODUCESLocally validated intent
Accepted · rejected · degraded · expired · locally overridden · reconciled outcome
EXAMPLE
A drone gateway accepts a signed survey envelope, enforces geofence and time locally, and never puts AI inside the flight-control loop.
DOMINANT RELATIONSHIPS
Agate→Sapphire→Onyx→Lodestone gateway→device controller→Amber
AMBER
RECORD // LINK // VERIFY
Amber
Preserve evidence of governed transitions without turning audit into a second data leak.
MATERIAL LOGIC // Amber can preserve inclusions and traces of an earlier environment. It represents retained evidence and lineage—not a claim that amber itself is immutable.
CONTROLSEvidence semantics
Event schema · lineage · correlation · privacy class · checkpointing · retention · export
RECEIVESGoverned transitions
Identity · policy decision · disclosure · release · capability · action · observed outcome
PRODUCESTamper-evident evidence
Privacy-aware receipts · linked lineage · signed checkpoints · SIEM and case exports
EXAMPLE
An investigator can prove who requested what purpose, which policy and model release applied, what action was attempted, and the observed result—without placing raw secrets in normal telemetry.
DOMINANT RELATIONSHIPS
every governed transition→Amber→checkpoint + lineage→SIEM / case / regulator export
ALLOY
INVENTORY // ABSTRACT // MIGRATE
Alloy
Make cryptography replaceable before replacement becomes urgent.
MATERIAL LOGIC // Alloys combine constituents to produce tailored properties. The metaphor fits hybrid classical/post-quantum profiles and algorithm agility; it does not claim every alloy is stronger than its ingredients.
CONTROLSCrypto policy
Algorithm profile · key purpose · provider · rotation · downgrade rules · recovery · deprecation
RECEIVESProtection requirements
Asset lifetime · confidentiality horizon · identity class · protocol maturity · module constraints
PRODUCESCrypto services
Keys · signatures · encryption · trust anchors · inventory · migration state · test evidence
EXAMPLE
A capability format keeps stable authority semantics while its signing profile migrates through tested, policy-controlled classical, hybrid, and later post-quantum configurations.
DOMINANT RELATIONSHIPS
crypto policy→Alloy provider abstraction→identities + grants + artifacts + evidence
PLATINUM
OWN // CHANGE // RESPOND
Platinum
Turn technical controls into an operable governance system.
MATERIAL LOGIC // Platinum is chemically stable, corrosion-resistant, and widely used as a catalyst. It represents durable oversight that enables controlled change—not a premium pricing tier.
CONTROLSOperational governance
Policy lifecycle · separation of duties · emergency mode · rollout · rollback · incident response
RECEIVESOrganizational intent
Risk appetite · regulatory duties · control ownership · exceptions · change approvals
PRODUCESGoverned configuration
Versioned bundles · staged rollout · ownership map · health state · exception register
EXAMPLE
A policy update is reviewed under separation of duties, canaried to one workflow, measured, then promoted or rolled back with evidence.
DOMINANT RELATIONSHIPS
governance intent→Platinum bundles→all domains→Amber operational evidence
COPPER
ADAPT // NORMALIZE // CONFORM
Copper
Connect existing systems without surrendering the control contract to any one vendor.
MATERIAL LOGIC // Copper is conductive, ductile, and used to connect systems. It represents versioned adapters that carry normalized signals across boundaries—not a place where authority should accumulate.
CONTROLSAdapter contracts
Versioning · schema · source attribution · conformance · retries · error semantics · health
RECEIVESExternal interfaces
IdP · data store · model API · KMS/HSM · tool · scheduler · device · SIEM
PRODUCESCanonical interfaces
Normalized identity · records · inference · actions · evidence · test results
EXAMPLE
Changing a model provider or identity platform requires a conformant adapter—not a rewrite of policy, capability, or evidence semantics.
DOMINANT RELATIONSHIPS
external systems↔Copper contracts↔FortEmerald domains
GARNET
ADMIT // QUARANTINE // EVALUATE // PROMOTE
Garnet
Govern how model releases are formed, evaluated, promoted, and retired.
MATERIAL LOGIC // Garnet is a mineral family whose growth zoning can record changing formation conditions. It represents model lineage and staged promotion—not a universal claim that all garnet “forms under pressure.”
CONTROLSRelease lifecycle
Dataset lineage · signed manifest · workload admission · quarantine · evaluation · promotion · retirement
RECEIVESCandidate evidence
Code · data declarations · base model · environment · metrics · safety tests · approvals
PRODUCESImmutable release identity
Signed manifest · evaluation record · promotion state · production eligibility · rollback target
EXAMPLE
A candidate is trained by a native scheduler, remains quarantined, passes independent evaluation and approval, then becomes an immutable release eligible for Opal routing.
DOMINANT RELATIONSHIPS
Garnet manifest→Agate + Sapphire→Silicon admission→quarantine + evaluation→Opal allowlist
21 // DOMINANT CONTROL RELATIONSHIPS
Four governed routes. Cross-cutting assurance throughout.
These arrows describe dominant control relationships, not packet flow. Amber records throughout; Alloy protects; Copper adapts; Platinum governs.
Minimum disclosure to eligible intelligence
Agate identity→Sapphire decision→Emerald capsule→Opal release→untrusted outputGarnet supplies release evidence; model output is validated again before any next use.
Proposal becomes narrowly authorized execution
Opal proposal + Agate→Sapphire obligations→Onyx capability→Titanium connectorHuman or multi-party approval is inserted where policy requires.
Cloud authority stops before local safety
Agate→Sapphire→Onyx signed envelope→Lodestone gateway→device controllerAI never enters the motor, actuator, flight, or other safety-critical control loop.
Formation evidence becomes production eligibility
Garnet manifest→Agate + Sapphire→Silicon admission→quarantine + evaluation→Opal allowlistNative schedulers retain placement; FortEmerald governs admission and promotion.
22 // MODEL ISOLATION + SOVEREIGNTY
Use the least-trusted model compatible with the permitted context.
FortEmerald does not promise that a model can reason over exact plaintext semantics while “knowing nothing.” It minimizes or tokenizes where possible and changes the execution boundary when sensitive semantics are essential.
External model
Commercial API receives a minimized capsule that excludes sensitive identifiers and source records.
- Provider contract enforced
- Audience-bound capsule
- No reusable secrets
Confidential endpoint
Approved release runs inside an attested confidential-compute boundary where available and validated.
- Environment attestation
- Customer-controlled keys
- Measured release identity
Sovereign model
Customer-controlled or air-gapped inference receives context that policy forbids from leaving the boundary.
- Local inference
- Private model registry
- Local evidence + export
No model
If no release and boundary satisfy policy, inference is denied or replaced with deterministic processing.
- Fail closed
- Escalate to human
- Deterministic fallback
SOURCE // NEVER SENT
EMERALD MINIMIZES →
unit=47
site=REDACTED
operator=REDACTED
fault=P-218MODEL CAPSULE // EXPIRING
PROPOSAL →
asset_class=rotor
condition=degraded
task=maintenance_plan
ref=ctx_7D2DETERMINISTIC RESOLUTION
ctx_7D2 resolved
only at connector
after capability check23 // LODESTONE EDGE MODEL // LATER EXTENSION
AI may shape intent. Deterministic controllers own safety.
The architecture separates probabilistic planning from bounded authority, local validation, and real-time control.
01 // AI OR HUMANPropose intentsurvey · inspect · reposition · report
→
02 // SAPPHIREDecide policypurpose · environment · operator · risk
→
03 // ONYXIssue envelopetarget · scope · time · limits · signature
→
04 // LODESTONEValidate locallytrust · freshness · geofence · health
→
05 // CONTROLLERExecute safelyreal-time loop · hard limits · emergency stop
OFFLINEPreviously issued envelopes remain narrow, short-lived, and locally revocable.
REVOCATIONExpiry and reconnect reconciliation limit dependence on continuous cloud reachability.
FAILUREUnknown authority fails closed; device safety behavior remains locally defined.
TELEMETRYEvidence records intent, validation, override, and outcome without exposing unnecessary payloads.
HUMAN CONTROLApproval and emergency override are explicit policy obligations, not prompt conventions.
BOUNDARYFortEmerald does not replace firmware, autopilot, PLC, RTOS, or certified safety systems.
24 // APPLICATION DOMAINS
One authority contract across data-heavy and machine-facing industries.
The common need is controlled disclosure, explicit delegation, deterministic action, and defensible evidence—not a single vertical workflow.
Network and service operations
Incident context · configuration proposals · privileged changes · multi-provider automation · outage evidence
Sensitive simulation and analysis
Compartmented scenarios · role-based disclosure · sovereign inference · bounded simulation actions · lineage
Fleet and mission intent
Signed task envelopes · geofences · offline limits · local safety · outcome reconciliation
Industrial and utility operations
OT context minimization · change approval · deterministic connectors · segmented edge enforcement
Protected decision support
Purpose-limited records · de-identification · eligible models · human approval · disclosure evidence
Regulated case automation
Case compartments · separation of duties · short-lived authority · explainable control path
Cross-system agent operations
Model routing · tool mediation · no ambient credentials · typed actions · linked control lineage
Model release governance
Dataset lineage · workload admission · quarantine · independent evaluation · controlled promotion
APPLICATION BOUNDARY: These are architectural applicability domains, not claims of current customers, contracts, certifications, field deployments, or defence capability.
25 // DEPLOYMENT + INTEROPERABILITY
The control contract travels. The sensitive boundary does not have to.
Deployment posture can be selected per workload while Copper adapters preserve the same authority semantics.
Managed service
Vendor-operated control plane with customer-side protected connectors.
Customer cloud
Customer VPC, VNet, or project with private data and model routes.
On-premises
VMs, Kubernetes, OpenShift, private models, and customer key services.
Air-gapped
Local identity, policy, inference, execution, evidence, and controlled updates.
Edge gateway
Signed envelopes, local enforcement, expiring authority, and reconnect reconciliation.
GOVERNANCE CONTROL PLANEFORTEMERALDidentity · policy · context · routing · capability · execution · evidence
COPPER ADAPTER CONTRACTSversioned · source-attributed · conformant · replaceable
IdPDataModelsKMS / HSMToolsSchedulersMachinesSIEM
BOUNDARY: FortEmerald governs admission and authority. Identity platforms, data stores, model providers, key systems, native schedulers, and device safety controllers keep their specialist roles.
26 // ALLOY CRYPTO RAIL
Post-quantum readiness begins with migration discipline—not a “Q-day” claim.
FortEmerald is designed to separate authority semantics from cryptographic providers so algorithms, protocols, hardware, and trust roots can change under policy.
Inventory + agility
- Crypto bill of materials
- Long-confidentiality data tags
- Provider abstraction
- Key-purpose separation
- Rotation + recovery exercises
Tested profiles
- NIST-standardized ML-KEM / ML-DSA / SLH-DSA
- Hybrid profile evaluation
- PKI + transport interoperability
- Downgrade resistance
- Performance + module constraints
Controlled migration
- Re-enrol identities
- Replace trust anchors
- Migrate firmware + secure boot
- Protect long-lived backups
- Disable retired algorithms
WORKLOAD IDENTITYPOLICY BUNDLESCAPABILITIESAUDIT CHECKPOINTSMODEL ARTIFACTSFIRMWARESIGNED INTENTBACKUPS
CLAIM BOUNDARY: “Post-quantum ready” means inventoried, replaceable, testable, and migration-governed. It does not mean the design is currently implemented, validated, or end-to-end post-quantum secure; protocol profiles remain maturity-dependent.
27 // PROJECT SCOPE + PLATFORM POSITION
Build the missing authority contract. Integrate the operating ecosystem.
The first validation target is deliberately narrow; the thirteen-domain architecture defines a much larger expansion ceiling.
One regulated workflow
One customer context · one IdP · one source · two model endpoints · one action connector · one evidence export
Portable semantics
Context capsules · canonical decisions · capabilities · governed intent · receipts · lineage · lifecycle gates
Existing systems
Identity · policy engines · KMS/HSM · models · tools · registries · schedulers · SIEM · device stacks
Land and extend
Workflow → connectors → providers → actions → agents → lifecycle → edge and machines
Enterprise control plane
Platform deployment · protected connectors · governed inference · controlled actions · private and air-gapped profiles
>_
MORE THAN A CONTENT FILTER. LESS THAN A REPLACEMENT PLATFORM.
FortEmerald targets the cross-system control boundary among identity, disclosure, intelligence, authority, execution, and evidence.
CURRENT STATUS: Phase 0 design architecture. No implementation, benchmark, customer, revenue, partnership, certification, production deployment, or validated commercial model is claimed.
28 // FOUNDER
David Buell
FOUNDER // FORTEMERALDOWNER + PRESIDENT // FOLDER FORT INC.
Québec-based technology entrepreneur with operating experience in cloud storage and current independent study spanning governed AI, secure systems, and next-generation cryptography.
PUBLIC OPERATING EXPERIENCE
- Owner + president · Folder Fort Inc.
- FolderFort.com · cloud storage platform
- Web, API, desktop, and mobile product operations
- Product launch · distribution · customer operations
CURRENT INDEPENDENT STUDY
- Post-quantum cryptography · crypto-agility
- Quantum communication · QKD concepts
- Secure systems · identity · authorization
- AI-native applications · agents · context isolation
FOUNDER ↔ SYSTEM FIT
Hands-on experience operating cloud data products informs FortEmerald’s emphasis on usable information boundaries, portable authority, controlled integration, and evidence.
PUBLIC RECORD Folder Fort · Product record · App Store · CIPO application 2413034
Ownership, FortEmerald founder role, and current study areas are founder-provided; public sources corroborate Folder Fort leadership and product activity.
29 // BUILD PATH
From control contract to governed autonomy.
A staged validation path keeps the first build measurable while preserving the broader FortEmerald architecture.
Protected AI + bounded software action
Identity · policy · context capsules · model gateway · capabilities · deterministic connector · evidence export
Lifecycle, compute, edge + machines
Model promotion · workload admission · private deployment · air gap · signed machine intent · local enforcement
Architecture baseline
Research · controls · threats · domains · material system
CURRENTCore contracts
Policy · capsule · release · capability · evidence · failure semantics
Vertical prototype
1 IdP · 1 source · 2 models · 1 action · 1 export
Regulated pilot
Measured disclosure · outage drills · control evidence · buyer outcomes
Platform expansion
Agents · lifecycle · schedulers · infrastructure · edge · machines
>_
FORTEMERALD // minimum context · bounded authority · deterministic action · defensible evidence.