The idea
MyFrontierAI is a personal AI operating environment: notes, projects, models, policies, and tools connected so that intelligence can work across context without making any single vendor, model, or platform the permanent center.
Sovereign by design. Frontier's governing policy requires a defined purpose, explicit authorization and an observable record for external processing. Implementation and enforcement are assessed separately from the written rule.
What Frontier is designed to support
Frontier is an evolving personal AI environment. Its Constitution defines the governing requirements; implementation proceeds through building, testing, observation and revision. A written policy alone is not evidence that a capability is operational or a control is enforced.
Second Brain (PARA + RAG)
Knowledge organized and made searchable by meaning, with explicit boundaries for what may be indexed, synchronized, or delegated.
Panel of Experts
Multiple local and external models used as interchangeable specialists, with disagreement and uncertainty preserved rather than flattened.
Personal AI Assistant
A human-directed assistant that can work from durable personal context while remaining constrained by policy, permissions, and oversight.
Sovereign Architecture
A zero-trust foundation combining local capability, network isolation, controlled delegation, backup, recovery, and auditability.
Capability status
Prepared September 14, 2026 from retained project records. Each status describes the bounded capability at its evidence date. This is not a live health report or a guarantee of current availability.
Operational: observed in use. Built and tested: demonstrated within a stated test scope. Designed: documented approach with deployment unverified. Proposed: a next step awaiting a decision and implementation.
| Capability | Status at evidence date | Dated evidence | Material limitation |
|---|---|---|---|
| Monitoring and daily digest | Operational | September 7, 2026: read-only audit observed the scheduled heartbeat and 15 active monitors. September 11: owner-reported notification delivery test. | Evidence covers the observed checks and delivery test, not every failure path, recovery or runtime enforcement. |
| Policy context at session startup | Built and tested | September 7, 2026: native startup traces and isolated filesystem allow/deny tests. | Verified in the tested sessions and permission profiles; written context is not a universal execution gate. |
| Independent architecture review | Built and tested | September 11, 2026: completed model review; exact input, native result and filed response verified. | A bounded review of the September 7 snapshot, not a fresh operational test or approval to deploy its proposals. |
| Durable workflow orchestration | Designed | September 11, 2026: recorded architecture decision retains workflow-specific orchestration as a candidate. | No deployed durable orchestration verified here; control-plane authority remains under review. |
| Broader automatic recovery | Proposed | September 11, 2026: audit reconciliation describes bounded, approved recovery playbooks as a next step. | No new recovery authority granted. A failed report does not itself enforce a stop or authorize repair. |
These are publishable summaries of private project records. Raw logs and protected configuration are not published. Capabilities without sufficient evidence are omitted; constitutional requirements remain governing requirements regardless of implementation status.
Built in the open
I publish selected artifacts and lessons from building Frontier, with dated evidence to distinguish what has been observed, tested, designed or proposed.
I am documenting the build, the failures, the governing decisions, and the lessons that emerge from creating a sovereign personal AI system in practice.