# Current Doctrine Index

Date: 2026-06-14

Project copy updated: 2026-06-23

## Current Restart Addendum

For `qne-node-v00600`, the active implementation context is the QNE
development-network bootstrap:

- Current network id: `qne-development-network`
- Current cloud roles: `development-master-0001`,
  `development-seed-master-0001`, `development-skill-repo-0001`
- Current seed endpoint: `development-seed-master-0001`
  `[2a01:4f9:c010:dc18::1]:7001`
- Current base-node layout: `~/QNE/qne-node/persist`,
  `~/QNE/runtimes/qne-node-v00601`, `~/QNE/users`, `~/QNE/logs`
- Current milestone uses qne-nodes only. User IDs and `users/<base36>` persist
  dirs are future work.
- Current installer doctrine is Rust-first. Bash, PowerShell, and batch
  installers are to be replaced by Rust binaries except for unavoidable tiny OS
  launchers.

See:

- `doctrine/qnerules.md`
- `doctrine/manifest/doctrine-structure-v20260623.md`
- `doctrine/manifest/conflict-and-promotion-log-draft-v20260623.md`

## Current Operational Doctrine

1. `../current/QNE_Installer_PA_First_Doctrine_V1.md`
   - Status: current operational doctrine
   - Layer: Layer B current support doctrine
   - Scope: public installer, PA-first first run, uninstall/rejoin, `~/QNE`, `~/QNE-keep`, `~/QNE-developer`, and developer/public root separation
   - Workspace anchor: qne-v225
2. `../current/QNE_Cross_Platform_Device_Vault_Doctrine_V1.md`
   - Status: current operational doctrine
   - Layer: Layer B current support doctrine
   - Scope: OS vault abstraction, cross-platform device secret custody, home-directory roots, and `dev_exchange_storage`
   - Workspace anchor: qne-v225
3. `../current/QNE_Main_Node_View_Session_System_Doctrine_V2.md`
   - Status: current superseding operational doctrine
   - Layer: Layer A/B bridge doctrine for current QNE node architecture
   - Scope: main nodes, master/seed/repository roles, `QNENodeSkill`, `QNESceneData`, `QNEViewSession`, `QNEMobileDeviceRecord`, `QNEMobileAdapter`, mobile/tablet clients, DHT delegated presence, and network startup/shutdown
   - Workspace anchor: qne-node-v00552, qne-view-session-v00500, qne-scene-renderer-skia-v00531
   - Supersedes: `../current/QNE_Main_Node_Shadow_System_Doctrine_V1.md`
4. `../current/QNE_Invite_Trial_Browser_View_Session_Doctrine_V2.md`
   - Status: current operational doctrine
   - Layer: Layer B current support doctrine under the main node view-session doctrine
   - Scope: Home Node invite flow, hosted trial users, browser QNEViewSessions, invitee mobile device records and mobile QNEViewSessions, PA-guided migration, invite QR/share behavior, and platform-hinted installer URLs
   - Workspace anchor: qne-node-v00552, qne-view-session-v00500, qne-scene-renderer-skia-v00531
   - Supersedes: `../current/QNE_Invite_Trial_Browser_Shadow_Doctrine_V1.md`
5. `../current/QNE_Cloud_Laptop_And_Remote_Assist_Doctrine_V1.md`
   - Status: current operational doctrine
   - Layer: Layer B current support doctrine under the main node view-session doctrine
   - Scope: temporary cloud laptop mode, VNC/noVNC boundaries, browser transport rule, QNE desktop feel, future video-first remote assist, paid helpers, media/screen capture direction, and migration to real user nodes
   - Workspace anchor: qne-node-v00509 and future cloud trial/remote-assist work
6. `../current/QNE_AI_Provider_Relay_Doctrine_V1.md`
   - Status: current planning doctrine
   - Layer: Layer B current support doctrine under the main node view-session doctrine
   - Scope: QNE AI provider capability, OpenAI relay as a `QNENodeSkill`, qne-p2p transport from Home Nodes to relay nodes, local Home Node token tally, scalable relay deployment, and future provider-operated QNE nodes
   - Workspace anchor: future qne-openai-relay skill work
7. `../current/QNE_User_Data_Import_Agent_Doctrine_V1.md`
   - Status: current planning doctrine and deferred work marker
   - Layer: Layer B current support doctrine under the main node view-session doctrine
   - Scope: user-authorized imports from social exports, bank transaction downloads, statements, contacts, calendars, and other user-owned data; future Obscura/browser automation behind a `QNEWebAgentEngine`; raw import provenance and read-only financial safety rules
   - Workspace anchor: future qne-user-data-import skill work after mobile PA usability and Home Node semantic action transport are stable
8. `../current/QNE_OpenClaw_Capability_Replacement_Investigation_V1.md`
   - Status: current planning doctrine and TODO marker
   - Layer: Layer B current support doctrine under the main node view-session doctrine
   - Scope: investigation of OpenClaw-style methods and capabilities for replacement with QNE-native Home Node, PA scene, QNENodeSkill, persist, qne-p2p, mobile view session, and AI relay code; replacement matrix for agent capability expansion
   - Workspace anchor: future QNE agent capability planning after mobile PA usability and Home Node semantic action transport are stable
9. `../current/QNE_Password_Record_Login_Recipe_Doctrine_V1.md`
   - Status: current planning doctrine and TODO marker
   - Layer: Layer B current support doctrine under the main node view-session doctrine
   - Scope: password records with vault secret references, structured login recipes, per-site login/autofill/submit/session policy, provenance metadata, and future Obscura-assisted login-flow discovery
   - Workspace anchor: future QNE password manager/vault work after mobile PA, Home Node semantic action transport, and initial vault structures are stable
10. `../current/QNE_Codex_Development_Network_Agent_Doctrine_V1.md`
   - Status: current operational doctrine
   - Layer: Layer B current support doctrine for the v00600 development network
   - Scope: Codex install/auth status checks, remote-device approval envelope,
     qneskill message/action boundary, and prohibition on copying Codex
     credentials or account tokens
   - Workspace anchor: qne-node-v00600, qneskill-codex-bootstrap-v00600
11. `../current/QNE_Contact_Node_NAT_And_Mobile_Backup_Doctrine_V1.md`
   - Status: current planning doctrine
   - Layer: Layer B current support doctrine for development-network
     reachability and persist recovery
   - Scope: contact-node NAT traversal, DHT endpoint leases, WAN/LAN installer
     status language, mobile recovery vault role, companion encrypted backup
     continuity, fixed-node lifetime storage policy, and backup manifests
   - Workspace anchor: qne-node-v00616+ networking, future QNE mobile app,
     persist backup and restore/migration work

## Relationship Rule

Current operational doctrine files in this directory are not replacements for older archived canonical packs unless explicitly marked as superseding. `QNE_Main_Node_View_Session_System_Doctrine_V2.md` is explicitly superseding for QNE node/system architecture and must be reconciled into future canonical doctrine indexes when QNE doctrine tooling is formalized. V1 shadow-named doctrine files remain historical records.
