Valdris.ai Foundation

AI Team OS Command Center

Active gate

VAL-478

Proof block

VAL-232

Blockers

Proof state

Locked

Public proof is locked

No website proof page, case study, public metric, client claim, or install-ready claim ships before VAL-232 passes.

Current Truth

VAL-250Scaffold only

Core asset kit exists. It is not install-ready proof.

VAL-249Blocked

Do not unblock until independent operator proof passes.

VAL-464Not passed

Independent operator test is still an active proof gate.

VAL-478Next action

Tester selection is the next real proof-path action.

VAL-232Public claims blocker

No public proof claims until this passes.

Next Action

VAL-478Next proof-path action

Select independent operator tester

Owner: OS Owner / AI Ops Lead

Why this is next: VAL-464 cannot run, and VAL-249 cannot unblock, until an independent tester is selected through VAL-478.

Output: A tester is selected, given the install surface, and assigned the independent operator run.

Blockers

Blocker	Affected Work	Owner	Source	Age	Resolution Path
VAL-232 Blocking	Public proof claims blocked Website proof, case studies, public metrics, install-ready claims	Founder / CEO Boundary	Current truth / proof gate policy	Open until proof bank is approved	Classify and approve proof claims before publishing.
VAL-249 Blocking	Install readiness blocked Install-ready status and operator handoff claims	Client Delivery Systems Lead	Current truth / install gate	Open until independent operator proof passes	Keep blocked until independent operator proof passes.
VAL-464 Blocking	Independent operator test not passed VAL-249 unblock path	Quality Enablement Lead	Current truth / independent operator test	Open until a pass result is recorded	Prepare and run the independent operator test after VAL-478.

Active Gates

Gate	State	Owner	Evidence	Next Action
VAL-478	Next action Tester not selected	OS Owner / AI Ops Lead	Current proof path starts here.	Choose the independent tester and run setup.
VAL-464	Not passed Independent operator proof has not passed	Quality Enablement Lead	No pass result is recorded.	Prepare the test after tester selection.
VAL-249	Blocked Depends on VAL-464	Client Delivery Systems Lead	Install-ready status is not approved.	Do not unblock until VAL-464 passes.
VAL-232	Blocked Public claims are not approved	Founder / CEO Boundary	No public proof claims are allowed.	Keep public proof surfaces gated.

Proof Status

Gate	Claim Surface	Evidence	Approval State	Public-Use Boundary
VAL-478	Tester selection is the next proof-path action	No selected independent operator is recorded.	Open / next action	Internal routing only. Do not present as operator proof.
VAL-464	Independent operator can run the install surface	No pass result is recorded.	Not passed	No public use. This must pass before install-ready language.
VAL-249	Install-ready operator handoff is approved	Blocked until independent operator proof passes.	Blocked	No install-ready claim until VAL-464 passes.
VAL-232	Website proof, case studies, public metrics, client claims	Public proof claims are not approved.	Blocked	No public proof claims before VAL-232 passes.
VAL-250	Core asset kit exists	Scaffold and core assets exist.	Scaffold-complete only	Internal source asset only. Do not use as install-ready proof.

Client / Install Switcher

Valdris

Company operating instance

Active foundation build

Owner: Founder / CEO Boundary
Scope: Company, offer, operating manual, app, website, proof gates, and delivery governance.
Source Policy: Use Notion and Linear as live operating sources. Use GitHub for application source.
Boundary: This is the company system. Do not mix client-specific evidence into public proof.

Valdris Seed Data

Seed Batch

valdris-foundation-seed-2026-05-21

Instance

Valdris

Control

VAL-710

Status

Review

Internal operator seed only. This does not prove install readiness or public claims.

Source	Record	Approved Use	Link
Notion	AI Team OS home Workspace root, canonical navigation, current proof path, source/history boundary.	Operator root and navigation source.	Source link
Notion	00 Command Center First landing page for status, blockers, next action, and operating traceability.	Current command surface.	Source link
Notion	AI Team OS Operator Index v1.0 Candidate operator interface for independent operator testing.	Navigation and operator test surface only. Independent proof has not passed.	Source link
Notion	03 Foundation / Primitives Foundation rules, primitives, source maps, and approval-linked records.	Foundation source-map parent and rule reference.	Source link
Linear	VAL-710 Execution control for seeding Valdris operating data into the app.	Task control and status trail.	Source link
GitHub	nickcarmonadigital/valdris-ai-team-os Private application source and implementation history.	App source and validation evidence.	Source link
Vercel	valdris-ai-team-os production deployment Production deployment target for the operator command center.	Runtime availability evidence only.	Source link

Area	Seeded Data	Operator Use	Boundary	Source
Operator root	AI Team OS is the main Valdris operating-system workspace. Linear tracks the work, Notion holds durable outputs, and Markdown remains the AI-readable backup.	Start here to locate the live command surface, source areas, install system, offer/proof area, and archive.	Do not treat source/history pages as live operator instructions unless the Command Center or Operator Index routes there.	AI Team OS home
Command surface	00 Command Center is the first place to land when checking status, next action, blockers, and operating traceability.	Use it before touching Notion moves, Linear status, proof gates, install assets, or public claims.	If another artifact conflicts with the current truth freeze, the current truth freeze wins.	00 Command Center
Current proof path	VAL-478 -> VAL-464 -> VAL-470 through VAL-477 -> VAL-249 decision.	Use this sequence to route independent operator proof work.	Do not unblock VAL-249 before VAL-464 records a valid pass result.	AI Team OS home / 00 Command Center
Public proof lock	VAL-232 -> approved claim language -> website / sales assets.	Route every public claim, case study, proof page, and metric through VAL-232.	No public proof claims, install-ready claims, case studies, client logos, or metrics before VAL-232 passes.	AI Team OS home / 00 Command Center
Operator interface	AI Team OS Operator Index v1.0 is the candidate front door for independent operator testing.	Use as the testable navigation surface after the Command Center status check.	Candidate interface only. Independent operator proof has not passed.	AI Team OS Operator Index v1.0
Department OS set	Delivery OS, Product OS, Engineering OS, Platform OS, QA / Training OS, RevOps OS, People / Ops / Admin OS, and CEO Pulse.	Use as the top-level company operating map for role and workflow routing.	Manual existence is source structure, not install-ready proof.	Operator Index / Department Operating Manuals
Role manual set	Client Delivery Systems Lead, AI Product Operator, Product Engineer, AI SRE / Platform Engineer, Quality Enablement Lead, Revenue Systems Operator, OS Owner / AI Ops Lead, and Founder / CEO Boundary.	Route work through role ownership, handoff, escalation, and approval boundaries.	No role can approve proof claims or install readiness outside its gate.	Operator Index / Role Operating Manuals
Workflow routes	VS-002 onboarding / first value, VS-003 request / build, VS-004 change / incident, VS-005 proof / pulse, weekly OS review, and tool/source request.	Use route IDs to assign agents, prompts, SOPs, outputs, gates, and handoffs.	Agents must not start from generic prompts; they must operate from route, role, task, and gate context.	AI Team OS Operator Index v1.0
Source/history boundary	01 Source Evidence, 02 Source Synthesis, reconstruction reports, legacy phase notes, and 99 Archive are source/history unless explicitly routed by the Command Center or Operator Index.	Use source/history for rationale, extraction, and traceability.	Source/history does not override current Notion and Linear truth.	AI Team OS home
App deployment	Production command center is deployed at valdris-ai-team-os.vercel.app with health checks and monitoring/logging surfaced.	Use production runtime only as app availability evidence.	Deployment proves app availability, not install readiness or public proof.	VAL-706 / VAL-708 source maps
App test coverage	App validation covers core data model, import mappers, contradiction detection, operator views, monitoring/logging, and health endpoint.	Use as app implementation coverage evidence for foundation execution.	Tests prove coverage only. They do not pass VAL-464 or unblock VAL-249.	VAL-709 source map

Utari Seed Data

Seed Batch

utari-pilot-seed-2026-05-21

Instance ID

UTARI-PILOT-2026

Instance

Utari Pilot / Source Instance

Control

VAL-711

Status

Review

Separated pilot/source seed only. Do not merge into Valdris company canon, public proof, or install readiness.

Source	Record	Approved Use	Link
Notion	VAL-637 Utari Operating Instance Separation Current Utari instance boundary standard and source classification rule.	Utari boundary source. Approval row remains open.	Source link
Notion	VAL-637 Approval Row Approval control for the Utari boundary standard.	Review-state control. Not a Done or public-use approval.	Source link
Notion	VAL-636 Valdris Operating Instance Separation Separates Valdris company OS from Utari pilot/source material.	Cross-instance boundary reference.	Source link
Notion	VAL-662 App Instance Model Defines app instance types, required fields, and data isolation rules.	App instance model reference.	Source link
Linear	VAL-711 Execution control for seeding Utari data into the app.	Task control and status trail.	Source link

Area	Seeded Data	Operator Use	Boundary	Source
Instance identity	UTARI-PILOT-2026 is the canonical identifier for the Utari Pilot / Source Instance.	Use this ID when routing Utari pilot/source material, source maps, proof records, and reusable lesson candidates.	This creates an app seed boundary only. It does not create a live client shell or public case study.	VAL-637 Utari Operating Instance Separation
Instance classification	Utari is classified as Pilot Source / History / Internal Evidence with Internal Only proof default.	Use Utari records for internal lessons, replay evidence, and source classification.	Do not treat Utari as Valdris company ownership, generic install readiness, or future-client default.	VAL-637 Utari Operating Instance Separation
Allowed contents	Utari pilot runbook, validation, retro ADR, minimum operating spine lessons, handoff examples, workflow replays, and source-of-truth gaps.	Keep these records in the Utari instance unless a current Linear issue routes a reusable extraction.	Do not copy raw client/private material into the Valdris company seed or public surface.	VAL-637 Utari Operating Instance Separation
Excluded contents	Valdris company baseline ownership, generic Delivery OS install readiness, future-client assumptions, public case-study language, public proof claims, website copy, and Valdris legal/commercial terms.	Use this exclusion list before promoting any Utari-sourced pattern.	Do not promote Utari-specific facts into reusable doctrine without change control.	VAL-637 Utari Operating Instance Separation
Promotion rule	A reusable lesson can move into AI Team OS doctrine only when the source artifact is linked, classification is stated, Utari-specific facts are separated, a current Linear issue routes the promotion, and approval is linked.	Use this rule for any proposed pattern extracted from Utari.	Promotion does not clear VAL-232, VAL-464, or VAL-249.	VAL-637 Utari Operating Instance Separation
Public proof rule	Utari can support internal learning and internal proof classification only by default.	Route any named client reference, proof claim, screenshot, testimonial, metric, or case-study language through VAL-232.	No Utari public proof use without exact claim and surface approval.	VAL-637 Utari Operating Instance Separation
App instance model	Utari is a distinct app instance type with its own source roots, proof records, claim boundaries, archive rules, and data isolation.	Use the app instance model to keep Utari separate from Valdris, templates, and future client instances.	Proof and claim records are instance-scoped unless explicitly promoted through approval.	VAL-662 App Instance Model

Truth Validation

Batch

truth-validation-2026-05-21

Control

VAL-712

Date

2026-05-21

Status

Review

Queued

Validation queues contradictions and guardrails. It does not pass VAL-464, unblock VAL-249, or approve public claims.

Subject	App Truth	Notion Truth	Linear Truth	Decision
VAL-250Blocking	Scaffold only	Scaffold/core-asset-complete only; not install-ready proof.	Done	Treat Linear Done as asset-kit completion only. Do not convert it into install-ready language. Keep the app, Notion, and Linear comments explicit that VAL-250 is not install-ready proof.
VAL-249Blocking	Blocked	Open and blocked until independent operator proof passes.	In Progress	Treat the issue as active but blocked. Do not unblock or close it before VAL-464 records a pass. Queue a Linear reconciliation comment that states blocked-by-VAL-464 without changing status to Done.
VAL-464Blocking	Not passed	Independent operator test has not passed.	Todo	No contradiction. Todo maps to not-run and not-passed for this gate. Keep visible as the active proof gate after VAL-478 tester selection.
VAL-478Blocking	Next action	Next real proof-path action.	Todo	No contradiction. Todo means the next action is still unexecuted. Keep top-of-command-center until tester, surface, schedule, and VAL-470 start decision are recorded.
VAL-232Blocking	Public claims blocker	No public proof claims until VAL-232 passes.	Todo	No contradiction. Todo preserves the public proof lock. Keep website proof, case studies, client claims, public metrics, and install-ready public language locked.
Proof path sequenceReview	VAL-478 -> VAL-464 -> VAL-470 through VAL-477 -> VAL-249 decision	00 Command Center compresses the path as VAL-478 -> VAL-464 -> VAL-249; AI Team OS home expands the child tests.	VAL-470 through VAL-477 are queued proof-path children.	Not a conflict. Use the expanded path in the app so operators see the test sequence. Keep compressed and expanded paths source-mapped to avoid a second proof path.

Contradiction Queue

Item	Action	Do Not Cross
VAL-249 blocked-state mismatch Blocking / Queued / Client Delivery Systems Lead	Preserve blocked interpretation; draft Linear comment linking VAL-249 to VAL-464 pass evidence.	Do not unblock, close, or call install-ready before VAL-464 passes.
VAL-250 done-state interpretation risk Blocking / Queued / Product Engineer	Preserve scaffold-only language everywhere VAL-250 appears.	Do not use Done as install-ready proof.
Proof path compressed-versus-expanded wording Review / Mapped / Quality Enablement Lead	Use the expanded sequence in operator UI and keep the compressed Command Center path as shorthand.	Do not create a parallel proof path outside VAL-478, VAL-464, and VAL-470 through VAL-477.

Clean Checks

VAL-464 status mappingClean

Linear Todo and app Not passed both mean no pass evidence is recorded.

VAL-478 next-action mappingClean

Linear Todo and Notion next-action language both point to unfinished tester selection.

VAL-232 public-proof lockClean

Linear Todo, Notion blocker language, and app lock all keep public proof disabled.

Sources Checked

Notion: 00 Command Center

Primary command-state reference.

Notion: AI Team OS home

Workspace root and proof-path navigation reference.

Linear: VAL-250

Asset-kit completion record; not install readiness proof.

Linear: VAL-249

Install-readiness gate and blocker record.

Linear: VAL-464

Independent operator proof gate.

Linear: VAL-478

Current next action.

Linear: VAL-232

Public proof and claim approval gate.

OS Tree View

Area	Contents	Operator Use	Boundary
Foundation	Rules, primitives, source-of-truth policy, proof gates, approval standards	Defines how every other OS surface is allowed to change.	Live canon only. Historical notes move to Archive / History.
Departments	Delivery OS, Product OS, Engineering OS, Platform OS, QA / Training OS, RevOps OS, People / Ops / Admin OS, CEO Pulse	Gives each department its manual, workflow routes, ownership, and cadence.	Department manuals must not duplicate role manuals or SOPs.
Roles	Client Delivery Systems Lead, AI Product Operator, Product Engineer, AI SRE / Platform Engineer, Quality Enablement Lead, Revenue Systems Operator, OS Owner / AI Ops Lead, Founder / CEO Boundary	Shows who owns decisions, handoffs, checks, and escalation.	Role pages define accountability; they do not become task backlogs.
Routes	Onboarding, request/build, change/incident, proof/pulse, weekly review, tool/source request	Routes incoming work to the right lane and proof gate.	Routes describe flow. Linear tracks execution.
SOPs	Process docs, handoffs, reconciliation, proof gates, install packet, app sync review	Turns repeatable work into final-draft operating procedure.	SOPs stay procedural and concise. Source artifacts stay linked, not copied.
SkillCards	process-doc, process-optimization, prompt-to-skill mappings, SOP-to-route mappings	Packages reusable operator skills with trigger, input, output, and route.	SkillCards are execution helpers, not strategy docs.
Proof	Proof gates, proof snapshots, claims bank, case study boundaries, public-use approval	Controls what can be claimed, where it can be used, and what evidence backs it.	No public proof claims before VAL-232 passes.
Archive / History	Reconstruction notes, older handoffs, duplicated drafts, source artifacts, superseded plans	Keeps historical context findable without letting it drive current operations.	Do not delete. Park, link, and mark source/history.

Foundation View

Rules

Hard constraints that govern the operating system.

VAL-250 is scaffold-complete only, not install-ready proof.
VAL-249 stays blocked until independent operator proof passes.
VAL-464 has not passed.
VAL-478 is the next real proof-path action.
VAL-232 blocks every public proof claim.

Primitives

Reusable building blocks every OS surface is made from.

Source
Route
Role
SOP
SkillCard
Proof gate
Approval row
Archive / History lane

Governance

Controls that keep the manual and execution system clean.

Use KEEP / MERGE / CLOSE / PARK for loose pages and issues.
Do not delete Notion source artifacts.
Do not mark Linear Done until the approval row is answered.
Every app task gets source map, approval row, mutation draft, and comment.

Source-of-Truth Policy

Defines which system is allowed to own which kind of truth.

Notion owns operating docs, source maps, approval logs, and manual surfaces.
Linear owns execution state, proof gates, comments, and task traceability.
GitHub owns app source, commits, and code review history.
Vercel owns preview and production deployment after validation.

Department View

Delivery OS

Client Delivery Systems Lead

Workflows: Intake, kickoff, access, install packet, handoff, weekly client operating review
SOPs: Sales-to-delivery handoff, client onboarding, install packet, proof snapshot, renewal path
Mermaid Diagram: Rendering diagram

Product OS

AI Product Operator

Workflows: Problem framing, MWP routing, spec creation, acceptance criteria, product feedback loop
SOPs: Source ingest, route card creation, prompt-to-skill mapping, product decision log
Mermaid Diagram: Rendering diagram

Engineering OS

Product Engineer

Workflows: Build request, implementation, review, validation, release note, app sync review
SOPs: Implementation handoff, code review, validation ladder, GitHub reference import, app sync review
Mermaid Diagram: Rendering diagram

Platform OS

AI SRE / Platform Engineer

Workflows: Environment setup, access control, deployment, monitoring, incident response
SOPs: Environment and secrets policy, access checklist, Vercel deployment, monitoring, incident escalation
Mermaid Diagram: Rendering diagram

QA / Training OS

Quality Enablement Lead

Workflows: Independent operator test, operator training, checklist review, pass/fail decision
SOPs: Mock operator test runner, proof gate SOP, training checklist, pass/fail review
Mermaid Diagram: Rendering diagram

RevOps OS

Revenue Systems Operator

Workflows: Lead capture, qualification, CRM updates, proposal, follow-up, proof-safe claims
SOPs: Discovery call script, qualification form, CRM tracker, proposal template, follow-up cadence
Mermaid Diagram: Rendering diagram

People / Ops / Admin OS

OS Owner / AI Ops Lead

Workflows: Internal cadence, access, contractor onboarding, retention, archive hygiene
SOPs: Weekly reconciliation, contractor onboarding, security/access, data retention, archive policy
Mermaid Diagram: Rendering diagram

CEO Pulse

Founder / CEO Boundary

Workflows: Weekly pulse, decision review, proof claim approval, capacity, boundary calls
SOPs: Founder pulse, claim approval, capacity plan, CEO boundary, monthly manual cleanup
Mermaid Diagram: Rendering diagram

Role View

Client Delivery Systems Lead

Responsibilities: Owns client delivery flow, install readiness, handoffs, and client operating cadence.
Inputs: Qualified client, signed scope, intake pack, access checklist, current proof gates
Outputs: Client command center, install packet, handoff record, weekly delivery pulse
Handoffs: Receives from RevOps OS. Hands install work to Product, Engineering, Platform, and QA lanes.
Escalation Path: Escalate scope, proof, or client boundary conflicts to Founder / CEO Boundary.

AI Product Operator

Responsibilities: Turns client or internal problems into routes, specs, acceptance criteria, and reusable patterns.
Inputs: Source artifacts, MWP route, client pain, operator feedback, proof constraints
Outputs: Route card, spec, acceptance criteria, reusable product pattern, SkillCard mapping
Handoffs: Hands scoped work to Product Engineer and proof requirements to Quality Enablement Lead.
Escalation Path: Escalate unclear ownership or productization calls to OS Owner / AI Ops Lead.

Product Engineer

Responsibilities: Builds app surfaces, integrations, automations, importers, and client/internal tools.
Inputs: Approved spec, data model, source map, validation requirements, repo state
Outputs: Code change, tests, commit, GitHub reference, implementation note
Handoffs: Receives from AI Product Operator. Hands deployment and runtime work to Platform.
Escalation Path: Escalate technical blockers, unsafe data flow, or missing acceptance criteria to Product and Platform owners.

AI SRE / Platform Engineer

Responsibilities: Owns environment, access, deployment, observability, incident response, and platform reliability.
Inputs: Validated build, env requirements, secrets policy, deployment target, monitoring needs
Outputs: Deployment, env config, monitoring signal, incident record, access boundary
Handoffs: Receives build artifacts from Engineering. Hands runtime status to Delivery and CEO Pulse.
Escalation Path: Escalate incidents, access risk, or production blockers to Founder / CEO Boundary.

Quality Enablement Lead

Responsibilities: Owns operator tests, training, proof gates, checklists, and pass/fail decisions.
Inputs: Install surface, test script, proof gate, operator feedback, acceptance criteria
Outputs: Test result, training gap, proof evidence, pass/fail decision, remediation path
Handoffs: Receives install surface from Delivery and Engineering. Hands proof decision to Delivery and CEO Pulse.
Escalation Path: Escalate failed proof, ambiguous evidence, or unsafe claims to Founder / CEO Boundary.

Revenue Systems Operator

Responsibilities: Owns lead flow, qualification, CRM hygiene, proposals, follow-up, and proof-safe sales language.
Inputs: Lead source, qualification form, offer scope, proof-approved claims, follow-up cadence
Outputs: Qualified opportunity, CRM record, proposal, kickoff handoff, sales notes
Handoffs: Hands qualified client and context to Client Delivery Systems Lead.
Escalation Path: Escalate pricing, legal, scope, or proof-claim risk to Founder / CEO Boundary.

OS Owner / AI Ops Lead

Responsibilities: Owns the operating manual, source hygiene, reconciliation, approvals, and system coherence.
Inputs: Notion docs, Linear state, GitHub changes, proof gates, approval rows
Outputs: Clean canon, source map, approval log, reconciliation decision, operating cadence
Handoffs: Coordinates across every role lane and keeps source/history separated from live canon.
Escalation Path: Escalate company boundary, claim approval, and final operating decisions to Founder / CEO Boundary.

Founder / CEO Boundary

Responsibilities: Owns final boundary calls, public proof approval, offer direction, capacity, and company priorities.
Inputs: CEO Pulse, proof evidence, capacity signal, client risk, claim approval requests
Outputs: Decision, approval, constraint, public claim boundary, priority call
Handoffs: Receives escalations from all role lanes and returns explicit decision boundaries.
Escalation Path: No higher internal escalation. Park unresolved risk until the decision is made.

Workflow Route View

MWP Route	Trigger	Owner	Handoff	Proof Output	SOP Links
VS-002 Onboarding / First Value	New client, new install instance, or first-value setup starts.	Client Delivery Systems Lead	RevOps hands qualified context to Delivery; Delivery routes setup needs to Product, Platform, and QA.	Client command center, access complete signal, first-value proof snapshot.	Client onboarding checklist, access checklist, install packet SOP, proof snapshot template
VS-003 Request / Build	Client or internal operator requests a workflow, tool, integration, app surface, or automation.	AI Product Operator	Product frames the route and acceptance criteria; Engineering builds; QA validates; Platform deploys when needed.	Route card, acceptance result, implementation note, validation record.	Source ingest SOP, implementation handoff, validation ladder, app sync review SOP
VS-004 Change / Incident	Breakage, access issue, source conflict, incident, material workflow change, or production risk appears.	AI SRE / Platform Engineer	Requester routes to Platform; Platform pulls Engineering or Delivery; CEO Boundary receives material risk.	Incident or change record, fix validation, source-of-truth update, stakeholder status.	Incident / escalation SOP, security / access SOP, source-of-truth policy, app sync review SOP
VS-005 Proof / Pulse	Proof checkpoint, weekly pulse, public claim request, case study request, or install-readiness claim appears.	Quality Enablement Lead	QA gathers evidence; Founder / CEO Boundary approves claims; RevOps and Website use only approved language.	Proof snapshot, gate decision, claim approval state, public-use boundary.	Proof gate SOP, proof snapshot template, claim approval standard, founder pulse template
Weekly OS Review Operating Review	Weekly operating cadence starts or stale Notion / Linear truth is detected.	OS Owner / AI Ops Lead	Department and role lanes report state; OS Owner reconciles; CEO Pulse receives decision needs.	Current truth update, blocker list, next action, reconciliation decisions.	Weekly Linear / Notion reconciliation, founder pulse template, monthly manual cleanup
Tool / Source Request Tooling and Source Intake	New source, connector, app, credential, document corpus, or archive candidate enters the system.	OS Owner / AI Ops Lead	Requester submits context; OS Owner classifies; Platform handles access; Product extracts reusable pattern.	Source map, permission record, KEEP / MERGE / CLOSE / PARK decision, archive boundary.	Source ingest SOP, access checklist, do-not-touch registry, archive policy

SOP Library

SOP	Owner	Status	Related Route	Source Link
Source Ingest SOP	OS Owner / AI Ops Lead	Final draft	Tool / Source Request	Notion: 03 Foundation / Primitives
Notion Canon Cleanup SOP	OS Owner / AI Ops Lead	Final draft	Weekly OS Review	Notion: Operator Index and 00 Command Center
Linear Reconciliation SOP	OS Owner / AI Ops Lead	Final draft	Weekly OS Review	Linear: Valdris.ai Foundation
Role Manual Creation SOP	OS Owner / AI Ops Lead	Final draft	Role View	Notion: Role manuals
Mermaid Diagram SOP	Quality Enablement Lead	Final draft	Department and Role views	Notion: Diagram system
Process Documentation SOP	AI Product Operator	Final draft	VS-003	Skill: process-doc
Process Optimization SOP	AI Product Operator	Final draft	VS-003	Skill: process-optimization
Proof Gate SOP	Quality Enablement Lead	Final draft / proof-gated	VS-005	Linear: VAL-232, VAL-249, VAL-464, VAL-478
Install Packet SOP	Client Delivery Systems Lead	Final draft / proof-gated	VS-002	Notion: 07 Install System
App Sync Review SOP	Product Engineer	Final draft	VS-003 / Weekly OS Review	GitHub: valdris-ai-team-os
Incident / Escalation SOP	AI SRE / Platform Engineer	Final draft	VS-004	Notion: Platform OS
Claim Approval SOP	Founder / CEO Boundary	Final draft / public-use locked	VS-005	Linear: VAL-232

SkillCard Library

SkillCard	Trigger	Input	Output	Route	Owner	Status
Process Documentation Skill: process-doc	A process lives in someone's head, needs handoff clarity, or must become an auditable SOP.	Process name, rough steps, current owner, handoffs, exceptions, metrics, and any existing notes.	Final-draft SOP with purpose, scope, RACI, process flow, detailed steps, exceptions, metrics, and related documents.	VS-003 / SOP + SkillCard System	AI Product Operator	Ready for operator use
Process Optimization Skill: process-optimization	A workflow is slow, unclear, overloaded with handoffs, or producing rework.	Current steps, owners, wait times, approvals, failure points, and operator pain.	Before/after process comparison, waste removal plan, automation candidates, impact estimate, and implementation plan.	VS-003 / Workflow Improvement	AI Product Operator	Ready for operator use
Source Ingest Notion: 03 Foundation / Primitives	A new doc, transcript, repo link, Linear issue, or source artifact enters the system.	Source URL or file, owner, date, scope, confidentiality boundary, and expected operating use.	Source map, KEEP / MERGE / CLOSE / PARK decision, archive boundary, and live-canon routing.	Tool / Source Request	OS Owner / AI Ops Lead	Ready for operator use
Notion Canon Cleanup Notion: Operator Index and 00 Command Center	A Notion page duplicates live canon, contradicts Linear, or mixes source/history with operator docs.	Page link, current claim, related Linear issue, source/history status, and target operator surface.	Cleanup decision, proposed move or merge, do-not-touch warning, and approval log entry.	Weekly OS Review	OS Owner / AI Ops Lead	Approval controlled
Linear Reconciliation Linear: Valdris.ai Foundation	Linear status, comments, milestone contents, or issue claims conflict with current truth.	Issue ID, current state, relevant Notion source, blocker chain, and recommended mutation.	Mutation draft, implementation comment, status recommendation, and done-transition boundary.	Weekly OS Review	OS Owner / AI Ops Lead	Approval controlled
Proof Gate Control Linear: VAL-232, VAL-249, VAL-464, VAL-478	An operator, client, website, or sales surface wants to claim proof, readiness, or install completion.	Claim text, evidence, gate issue, public-use surface, and approval owner.	Approved, blocked, internal-only, or parked claim decision with proof-path next action.	VS-005	Quality Enablement Lead	Proof-gated
Install Packet Builder Notion: 07 Install System	A client or internal instance needs a command center, active board, RACI, and Day 90 proof lane.	Instance name, owner, intake pack, board schema, access model, route map, and proof snapshot.	Install packet, client command center, active work board, RACI, cadence, and Day 90 scorecard.	VS-002	Client Delivery Systems Lead	Proof-gated
App Sync Review GitHub: valdris-ai-team-os	A Notion or Linear operating truth needs to be reflected in the application.	Task ID, source map, acceptance surface, repo state, tests, and deployment boundary.	Code change, validation result, commit, source map update, Linear comment, and review state.	VS-003 / Weekly OS Review	Product Engineer	Ready for operator use
Claim Approval Linear: VAL-232	A public page, proposal, case study, metric, testimonial, or sales claim needs proof language.	Draft claim, intended audience, evidence, source link, proof gate, and publication surface.	Public-safe language, sales-call-only language, internal-only note, or blocked claim record.	VS-005	Founder / CEO Boundary	Public-use locked

Prompt Registry

Prompt	Trigger	SkillCard	Route	Owner	Output	Guardrail
Document this process	A workflow needs to become a readable SOP, handoff doc, RACI, or audit-ready operating procedure.	Process Documentation	VS-003 / SOP + SkillCard System	AI Product Operator	Final-draft SOP with RACI, process flow, detailed steps, exceptions, metrics, and related documents.	Ask for missing owner, trigger, output, and exception context through the approval log before final close.
Optimize this workflow	A process is slow, unclear, manual, approval-heavy, or failing at handoffs.	Process Optimization	VS-003 / Workflow Improvement	AI Product Operator	Before/after comparison, waste map, automation candidates, impact estimate, and implementation plan.	Do not remove a control gate unless the replacement checkpoint preserves accountability.
Ingest this source	A new Notion page, markdown file, transcript, repo link, Linear issue, or outside artifact enters the OS.	Source Ingest	Tool / Source Request	OS Owner / AI Ops Lead	Source map, source/history classification, live-canon route, and KEEP / MERGE / CLOSE / PARK decision.	Do not treat source material as current truth until it is mapped against Notion and Linear.
Clean this Notion area	Notion pages are duplicated, stale, mixed with history, or confusing the operator interface.	Notion Canon Cleanup	Weekly OS Review	OS Owner / AI Ops Lead	Cleanup decision table, proposed moves, merge targets, archive candidates, and do-not-touch warnings.	Do not delete or move pages without approval. Park source/history instead of erasing it.
Reconcile this Linear issue	A Linear issue state, comment, milestone, or blocker chain conflicts with current truth.	Linear Reconciliation	Weekly OS Review	OS Owner / AI Ops Lead	Status recommendation, mutation draft, implementation comment, and done-transition rule.	Do not move an issue to Done until the matching approval row is answered and locked.
Can we claim this publicly?	A website, proposal, case study, sales page, or public proof surface wants to use a claim.	Claim Approval	VS-005	Founder / CEO Boundary	Public-safe wording, sales-call-only wording, internal-only note, or blocked claim record.	No public proof claim ships before VAL-232 passes.
Run the proof gate	Install readiness, independent operator proof, public proof, or claim approval needs a gate decision.	Proof Gate Control	VS-005	Quality Enablement Lead	Gate state, evidence record, pass/fail decision, next action, and public-use boundary.	VAL-249 stays blocked until VAL-464 passes, and VAL-478 remains the next proof-path action.
Build the install packet	A Valdris, Utari, or future-client instance needs command center, board, RACI, cadence, and scorecard surfaces.	Install Packet Builder	VS-002	Client Delivery Systems Lead	Install packet, client command center, board schema, OS Owner blueprint, proof snapshot, and Day 90 scorecard.	Do not claim install readiness from scaffold alone. VAL-250 remains scaffold-complete only.
Sync this into the app	A live operating truth needs an app surface, importer, registry, dashboard, or review queue.	App Sync Review	VS-003 / Weekly OS Review	Product Engineer	Code change, validation result, commit, Notion source map, Linear comment, and review state.	GitHub records implementation; Notion and Linear remain the live operating sources of truth.
Prepare weekly OS review	The weekly cadence starts or stale truth appears across Notion, Linear, GitHub, or the app.	Linear Reconciliation	Weekly OS Review	OS Owner / AI Ops Lead	Current truth, blocker list, next action, reconciliation queue, and approval questions.	Separate active proof gates from historical artifacts before changing statuses.

Handoff View

Handoff	From	To	Trigger	Required Package	Acceptance Check	Escalation	Proof Boundary
Sales to Delivery	Revenue Systems Operator	Client Delivery Systems Lead	A qualified client is ready for kickoff or proposal-to-delivery transition.	Qualified opportunity, offer scope, pricing terms, client context, proof-safe claims, access needs, and kickoff notes.	Delivery confirms scope, owner, first-value target, and client command center setup path.	Founder / CEO Boundary handles pricing, claim, scope, or legal conflicts.	No install-ready claim
Delivery to Product	Client Delivery Systems Lead	AI Product Operator	A client workflow needs route framing, MWP routing, acceptance criteria, or reusable pattern extraction.	Client problem, current workflow, desired outcome, users, constraints, source links, and proof requirements.	Product returns route card, acceptance criteria, owner map, and build/no-build decision.	OS Owner / AI Ops Lead resolves ownership and route conflicts.	Source mapped first
Product to Engineering	AI Product Operator	Product Engineer	A route, app surface, integration, automation, importer, or internal tool is approved for build.	Spec, acceptance criteria, source map, data model impact, proof constraints, test expectation, and repo target.	Engineering returns code, validation result, commit, implementation note, and unresolved risk list.	AI SRE / Platform Engineer joins for deployment, secrets, access, or runtime risk.	Validation required
Engineering to Platform	Product Engineer	AI SRE / Platform Engineer	A validated build needs deployment, environment work, monitoring, or access control.	Commit, build result, env needs, secret requirements, deployment target, rollback path, and monitoring signal.	Platform confirms deploy state, access boundary, logs/monitoring, and incident fallback.	Founder / CEO Boundary handles production-risk or access-risk decisions.	Deploy after validation
Engineering to QA	Product Engineer	Quality Enablement Lead	A build or install surface needs independent operator validation.	Test script, operator path, acceptance criteria, known constraints, source map, and expected evidence.	QA records pass, fail, or pass with caveats and returns remediation steps.	Founder / CEO Boundary handles disputed proof or unsafe claim pressure.	VAL-464 not passed
QA to Delivery	Quality Enablement Lead	Client Delivery Systems Lead	A proof gate or operator test produces a delivery-impacting decision.	Gate result, evidence, training gaps, remediation list, client-facing boundary, and next action.	Delivery updates install path, client cadence, and handoff language from the gate decision.	Founder / CEO Boundary decides public-use or readiness claims.	VAL-249 remains blocked until pass
OS Owner to CEO Pulse	OS Owner / AI Ops Lead	Founder / CEO Boundary	A weekly review, blocker, claim, capacity issue, or source conflict needs final boundary decision.	Current truth, blocker list, approval questions, recommended decision, and source links.	CEO Boundary returns approve, reject, park, or revise decision with a clear owner.	No higher internal escalation. Park unresolved risk.	Decision required
Proof to Public Surface	Founder / CEO Boundary	Revenue Systems Operator / Website	A proof-approved claim is allowed into a proposal, website, case study, or sales asset.	Approved claim language, evidence link, allowed audience, expiration or review date, and prohibited phrasing.	Public or sales surface uses only approved language and links back to the claim decision.	Founder / CEO Boundary owns final removal or revision decision.	VAL-232 controls public use

Proof Center

Surface	Gate	State	Evidence State	Allowed Use	Next Action
Tester selection	VAL-478	Next action	No selected independent operator is recorded.	Internal proof-path routing only.	Select the independent operator tester and assign the run path.
Independent operator proof	VAL-464	Not passed	No pass result is recorded.	Internal QA and remediation only. No install-ready claim.	Prepare and run the test after VAL-478 selects the tester.
Install readiness	VAL-249	Blocked	Blocked until independent operator proof passes.	Internal delivery planning only.	Keep blocked until VAL-464 passes.
Public proof claims	VAL-232	Blocked	Public claim bank is not approved.	No website proof, case study, public metric, client claim, or public-ready wording.	Classify claims and approve language before publishing.
Core asset kit	VAL-250	Scaffold-complete only	Core assets exist, but install-ready proof is not approved.	Internal source artifact and build reference only.	Do not use scaffold existence as proof of install readiness.
Sales-call proof language	VAL-232	Controlled	Sales-call-only wording requires claim classification.	Only approved, non-public language after claim review.	Route proposed language through Claim Approval before use.

Install Packet Generator

Valdris

Internal company operating packet for Valdris.ai foundation build, proof gates, and execution cadence.

Foundation packet

Owner: OS Owner / AI Ops Lead
Gate: Review packet only. It does not make Valdris install-ready or public-proof-ready.
Required Inputs: Current truth, Linear project state, Operator Index, Command Center, role manuals, route map, proof gates, and approval log.
Source Boundary: Use Valdris company canon only. Client-specific evidence stays out of public proof until approved.

Generated Sections

Command Center snapshot

Current truth and blocker list

Role ownership and handoff map

SOP and SkillCard routing

Proof Center and claim controls

Weekly OS review cadence

Mock Operator Test Runner

VAL-478

Tester selection

Next action

Operator: OS Owner / AI Ops Lead
Instruction: Select the independent operator, confirm access path, and assign the run packet.
Pass Criteria: Tester is named, access boundary is recorded, and the test packet is assigned.
Evidence Required: Tester name, date, source map link, and assignment note.
Boundary: This is the next real proof-path action. No downstream test starts before this is done.

KEEP / MERGE / CLOSE / PARK Review Table

Item	Type	Decision	Reason	Target Action	Owner	Approval State	Do Not Cross
AI Team OS home Notion	Operator page	KEEP	Top-level entrypoint for the operating manual and current operator interface.	Keep as the live entrypoint and link active operator surfaces from the Command Center.	OS Owner / AI Ops Lead	Review	Do not bury the live home under archive or reconstruction notes.
00 Command Center Notion	Operator page	KEEP	Live control surface for current truth, blockers, proof gates, and next action.	Keep current with VAL-478 as next action and proof blockers visible.	OS Owner / AI Ops Lead	Review	Do not point it back to stale VAL-246 routing.
Operator Index Notion	Operator page	KEEP	Index is the spine for role, SOP, SkillCard, workflow, proof, and archive navigation.	Keep as the operator map and connect it to app surfaces without duplicating task state.	OS Owner / AI Ops Lead	Review	Do not treat index links as proof that every page is final.
07 Install System Notion	Install canon	MERGE	Install system content should feed the Install Packet generator and proof path, not live as scattered drafts.	Merge reusable install packet content into the install canon and park superseded source notes.	Client Delivery Systems Lead	Review	Do not claim install-ready status from merged content alone.
Reconstruction spine pages Notion	Source/history	PARK	Useful historical context, but not the live operator interface.	Park under Archive / History with links back to extracted live canon.	OS Owner / AI Ops Lead	Review	Do not delete reconstruction material or let it override current truth.
VAL-250 Linear	Execution issue	KEEP	It records scaffold/core-asset completion and must stay bounded to that claim.	Keep as scaffold-complete only and reference from proof surfaces as non-install-ready evidence.	Product Engineer	Review	Do not relabel as install-ready proof.
VAL-249 Linear	Blocked gate	KEEP	Install readiness remains blocked until independent operator proof passes.	Keep blocked and only revisit after VAL-464 has a valid pass decision.	Client Delivery Systems Lead	Review	Do not unblock before VAL-464 passes.
VAL-464 Linear	Proof gate	KEEP	Independent operator test has not passed and controls downstream readiness.	Keep active and run through VAL-478 plus VAL-470 through VAL-477 sequence.	Quality Enablement Lead	Review	Do not mark passed from scaffold, docs, or app surface existence.
VAL-478 Linear	Next action	KEEP	Tester selection is the next real proof-path action.	Keep as the current next action until the independent tester is selected and assigned.	OS Owner / AI Ops Lead	Review	Do not start downstream proof claims before tester selection is recorded.
VAL-232 Linear	Public claim blocker	KEEP	Controls every public proof, case study, metric, client claim, and website proof surface.	Keep blocking public proof until claim bank classification and approval are complete.	Founder / CEO Boundary	Review	No public proof claims before VAL-232 passes.
Duplicate draft pages Notion	Loose pages	MERGE	Duplicates create operator confusion when they contain partial versions of live SOPs or role docs.	Merge useful content into the canonical page, then park the source page under Archive / History.	OS Owner / AI Ops Lead	Approval required	Do not delete; do not merge without source map and approval row.
Superseded Linear tasks Linear	Loose issues	CLOSE	Some older issues may be fully replaced by canonical foundation tasks or committed app surfaces.	Close only after linking the replacement issue, source map, and implementation comment.	OS Owner / AI Ops Lead	Approval required	Do not close active proof gates or blocked readiness issues.

Notion Cleanup Queue

Page / Area	Lane	Current Problem	Cleanup Action	Target Home	Owner	Approval	Boundary
AI Team OS home	Live operator interface	Can become a dumping ground if reconstruction notes and live navigation stay mixed.	Keep as the top entrypoint and expose only live operator links, current truth, and approved navigation.	AI Team OS home	OS Owner / AI Ops Lead	Review	Do not move, archive, or replace this page with a source artifact.
00 Command Center	Live operator interface	Stale next-action references can overwrite the active proof path.	Keep current truth visible and point next action to VAL-478 until tester selection is recorded.	AI Team OS home / Command Center	OS Owner / AI Ops Lead	Review	Do not revive stale VAL-246 routing or mark proof gates passed.
Operator Index	Live operator interface	Index links can make rough pages look final if they are not labeled by lane.	Separate links into operator pages, source/history, proof gates, SOPs, SkillCards, and archive.	Operator Index	OS Owner / AI Ops Lead	Review	Do not use linked-page existence as readiness proof.
03 Foundation / Rules / Primitives	Live canon	Rules, primitives, and historical rationale can blur together.	Keep current rules and primitives live; move extracted rationale into source/history links.	03 Foundation / Rules / Primitives	OS Owner / AI Ops Lead	Review	Do not weaken VAL-232, VAL-249, VAL-464, VAL-478, or VAL-250 rules.
04 Department Operating Systems	Live canon	Department pages can duplicate role manuals, SOPs, and workflow route cards.	Keep department ownership, workflows, cadence, and Mermaid diagrams; link role and SOP detail out.	04 Department Operating Systems	OS Owner / AI Ops Lead	Review	Do not let department pages become task backlogs.
05 Global Databases	Live canon	Database schemas and template rows can drift from the app and install packet surfaces.	Map each database to owner, purpose, source policy, and app/importer surface.	05 Global Databases	OS Owner / AI Ops Lead	Review	Do not import rows without owner, route, status, and proof boundary.
06 CEO / Executive Pulse	Live operator interface	Decision notes can sit outside approval and claim-control flow.	Keep CEO decisions, capacity calls, claim approvals, and escalation outcomes in one pulse lane.	06 CEO / Executive Pulse	Founder / CEO Boundary	Review	Do not publish claim language without VAL-232 approval.
07 Install System	Live canon / merge target	Install packet content can exist as scattered drafts instead of one controlled package.	Merge reusable install pack, intake pack, board schema, RACI, proof snapshot, and Day 90 scorecard into canon.	07 Install System	Client Delivery Systems Lead	Approval required	Do not claim install readiness from merged install docs alone.
08 Offer + Proof	Proof-controlled canon	Offer language and proof language can leak public claims before approval.	Separate offer copy, sales-call-only language, internal proof notes, and public-safe claims.	08 Offer + Proof	Founder / CEO Boundary	Approval required	No public proof claim before VAL-232 passes.
99 Archive / History	Archive	Archive rules are easy to skip when old pages still feel useful.	Use as the parking lane for reconstruction notes, superseded drafts, and extracted source artifacts.	99 Archive / History	OS Owner / AI Ops Lead	Review	Do not delete source/history pages; park and link them.
Reconstruction spine	Source/history	Historical reconstruction can be mistaken for the active operator interface.	Extract useful rules, routes, diagrams, and SOP inputs into live canon; park the source pages.	99 Archive / History	OS Owner / AI Ops Lead	Approval required	Do not let source/history override current Linear truth.
Loose duplicate pages	Cleanup queue	Duplicate drafts create competing versions of the same SOP, role manual, or install artifact.	Assign KEEP / MERGE / CLOSE / PARK, source-map useful content, then park or link the original.	KEEP / MERGE / CLOSE / PARK review table	OS Owner / AI Ops Lead	Approval required	Do not delete or move without approval.

Linear Reconciliation Queue

Issue / Group	Current Truth	Drift Risk	Recommended Handling	Mutation Type	Owner	Approval State	Do Not Cross
VAL-250	Scaffold/core-asset-complete only. It is not install-ready proof.	Can be misread as proof that the system is ready for operator install.	Keep current claim bounded, link to VAL-249 and VAL-464, and comment with scaffold-only language where needed.	Comment only	Product Engineer	Review	Do not convert scaffold completion into install-ready proof.
VAL-249	Open and blocked until independent operator proof passes.	Can be unblocked too early if app surfaces or Notion pages look complete.	Keep blocked and only revisit after VAL-464 records a valid pass result.	Keep current	Client Delivery Systems Lead	Review	Do not unblock before VAL-464 passes.
VAL-464	Independent operator test has not passed.	Can be treated as passed because the runner and test sequence now exist.	Keep active, attach the mock operator runner, and wait for evidence from VAL-478 plus VAL-470 through VAL-477.	Status + comment	Quality Enablement Lead	Review	Do not mark passed from docs, scaffold, or app UI existence.
VAL-478	Next proof-path action: select the independent operator tester.	Can get buried under downstream test tasks.	Keep as the current next action until tester selection and assignment are recorded.	Keep current	OS Owner / AI Ops Lead	Review	Do not start proof claims before tester selection is recorded.
VAL-232	Public proof claims remain blocked.	Website, offer, proposal, or case-study work can leak unapproved claims.	Keep blocking public proof and route claim language through approval.	Keep current	Founder / CEO Boundary	Review	No public proof claims before VAL-232 passes.
VAL-470 through VAL-477	Mock operator test sequence is queued behind VAL-478.	Individual test rows can be marked passed without full evidence.	Keep queued, run in order, attach evidence, and feed the final decision into VAL-464.	Comment only	Quality Enablement Lead	Review	Do not use partial test success to unblock VAL-249.
VAL-246	Stale next-action reference if it points operators away from VAL-478.	Can keep Command Center and Linear routing split across two next actions.	Park or close after confirming every live surface points to VAL-478.	Status + comment	OS Owner / AI Ops Lead	Approval required	Do not close until replacement links and source map are attached.
VAL-460 / VAL-462 / VAL-448 / VAL-449	Related reconstruction or prep issues require source/history classification.	Can duplicate live app/operator surfaces or imply older proof state.	Map each to KEEP, MERGE, CLOSE, or PARK after comparing against current Notion and app canon.	No mutation	OS Owner / AI Ops Lead	Approval required	Do not close or relabel until the replacement surface is named.
VAL-465 through VAL-469	Adjacent proof/setup issues need reconciliation against the mock operator sequence.	Can fragment the proof path outside VAL-478 and VAL-470 through VAL-477.	Park, merge, or link after confirming whether each issue is historical setup or active proof work.	No mutation	Quality Enablement Lead	Approval required	Do not create a second proof path outside the current sequence.
VAL-251 / VAL-252 / VAL-248 / VAL-247	Older install, source, or proof-related issues require loose-issue classification.	Can keep legacy task language alive after canonical app and Notion surfaces exist.	Audit and assign KEEP, MERGE, CLOSE, or PARK with replacement links before any status mutation.	No mutation	OS Owner / AI Ops Lead	Approval required	Do not close active dependencies or source records without approval.

Source / History Archive View

Artifact	Archive Lane	Extracted Canon	Status	Owner	Retrieval Rule	Boundary
Reconstruction spine pages	Reconstruction	Foundation rules, operator tree, department/role structure, proof path, and archive policy.	Park after extraction	OS Owner / AI Ops Lead	Retrieve only when a live page needs historical rationale or missing source context.	Do not let reconstruction text override current Notion and Linear truth.
Older handoff documents	Handoff history	Role handoff map, required handoff packages, escalation paths, and acceptance checks.	Park after merge	OS Owner / AI Ops Lead	Retrieve when a role or SOP handoff needs origin context or an edge-case exception.	Do not use older handoff language as a live SOP until it is merged into canon.
Daniel Miessler source notes	External source	Knowledge-work framing, AI-operator model, and company operating-system rationale.	Source reference	Founder / CEO Boundary	Retrieve for strategic framing, not for proof, client claims, or operational status.	External thought leadership is not Valdris proof and cannot bypass VAL-232.
Andrew Karpathy Obsidian/wiki notes	External source	Wiki-style knowledge structure, connected notes, and source-to-operator navigation pattern.	Source reference	OS Owner / AI Ops Lead	Retrieve when designing navigation, backlinks, source maps, and knowledge retrieval surfaces.	Do not treat inspiration notes as live Valdris canon without extraction.
YouTube/video research notes	External source	Supporting framing for AI team OS, operator interface design, and workflow bottleneck language.	Source reference	AI Product Operator	Retrieve only after the transcript or notes are source-mapped to a live task or SOP.	Do not use video summaries as proof claims or final operating procedure.
Duplicate SOP drafts	Superseded drafts	Final-draft SOP library entries and related route mappings.	Park after merge	OS Owner / AI Ops Lead	Retrieve when a final SOP needs a missing exception, metric, or handoff detail.	Do not keep multiple live SOP versions for the same process.
Duplicate role manual drafts	Superseded drafts	Role responsibilities, inputs, outputs, handoffs, escalation paths, and Mermaid diagrams.	Park after merge	OS Owner / AI Ops Lead	Retrieve when a role page needs missing accountability, boundary, or diagram context.	Do not let draft role pages become parallel operator interfaces.
Superseded Linear planning notes	Execution history	Replacement issue links, source maps, implementation comments, and final status rationale.	Reference only	OS Owner / AI Ops Lead	Retrieve when explaining why an issue was parked, merged, closed, or kept.	Do not reopen stale execution paths without a new approval row.
Client-specific source artifacts	Client source/history	Reusable patterns only after client-specific evidence is separated and approved.	Restricted source	Client Delivery Systems Lead	Retrieve only inside the matching client instance or approved reusable-pattern extraction.	Do not mix client-specific evidence into Valdris public proof or company canon.
Proof and claims source notes	Proof history	Claim classification, evidence links, public-safe wording, and blocked-claim decisions.	Proof-controlled	Founder / CEO Boundary	Retrieve only through the Proof Center or Claim Approval path.	No public proof claims before VAL-232 passes.

Do-Not-Touch View

Protected Item	Source / Gate	Severity	Prohibited Action	Allowed Path	Owner	Release Condition
VAL-232	Public proof lock	Hard block	Do not publish website proof, case studies, public metrics, client claims, or public-ready claim language.	Draft internal claim classifications and route language through Claim Approval.	Founder / CEO Boundary	VAL-232 passes with approved public-safe language.
VAL-249	Install readiness lock	Hard block	Do not unblock, close, or call the system install-ready before independent operator proof passes.	Keep blocked, collect evidence, and wait for VAL-464 decision.	Client Delivery Systems Lead	VAL-464 records a valid pass result with sufficient evidence.
VAL-464	Proof gate lock	Hard block	Do not mark passed from docs, app UI, scaffold completion, or partial test success.	Run the mock operator sequence and attach evidence from VAL-478 and VAL-470 through VAL-477.	Quality Enablement Lead	Full test run is scored as pass, fail, or pass with caveats.
VAL-478	Next-action lock	Blocking	Do not bury, skip, or replace tester selection with downstream proof tasks.	Select the independent operator tester and record assignment evidence.	OS Owner / AI Ops Lead	Tester is selected, access boundary is recorded, and the run packet is assigned.
VAL-250	Claim boundary	Blocking	Do not relabel scaffold/core-asset completion as install-ready proof.	Reference as scaffold-complete only and link to active proof gates.	Product Engineer	Independent proof path passes and readiness is separately approved.
Live Notion operator pages	Operator interface lock	Blocking	Do not move, archive, replace, or bury AI Team OS home, 00 Command Center, or Operator Index.	Update live links and source maps through approval-controlled edits.	OS Owner / AI Ops Lead	Nick approves a replacement operator interface and source map.
Source/history pages	No-delete lock	Blocking	Do not delete reconstruction notes, older handoffs, duplicate drafts, or historical source artifacts.	Park, link, source-map, and extract useful canon after approval.	OS Owner / AI Ops Lead	Source is extracted, linked, parked, and approved.
Utari/client-specific artifacts	Client boundary	Hard block	Do not merge client-specific evidence into Valdris company canon or public proof.	Keep inside the matching client instance or extract only approved reusable patterns.	Client Delivery Systems Lead	Reusable pattern is approved and client-specific evidence is removed.
Linear Done transitions	Approval row lock	Blocking	Do not move implementation issues to Done while the matching approval row is open.	Move to In Progress with implementation comment and wait for approval.	OS Owner / AI Ops Lead	Approval row is answered and locked.
Linear issue clusters marked for reconciliation	No-silent-mutation lock	Blocking	Do not close, cancel, relabel, or merge older issues without a source map and replacement link.	Draft mutation recommendations in Notion and wait for approval.	OS Owner / AI Ops Lead	Replacement issue, source map, and approval row are linked.
Public website/proof surfaces	VAL-232 publication lock	Hard block	Do not ship proof page, case studies, client logos, metrics, or install-ready language to the website.	Keep website proof content draft/internal and route every claim through Proof Center.	Founder / CEO Boundary	VAL-232 approves public-safe claim language before deploy.
Approval Log / Linear Mutation Drafts	Approval workflow lock	Blocking	Do not bypass approval rows, mutation drafts, or source maps for status changes and canon moves.	Create the approval row, source map, and mutation draft, then wait for the approval answer.	OS Owner / AI Ops Lead	Approval row is answered, locked, and linked to the mutation evidence.

Environment / Secrets Policy

Area	Owner	Required Control	Prohibited Action	Operating Action
Local development	AI SRE / Platform Engineer	.env.example tracks safe variable names; .env.local holds real local values and remains gitignored.	Do not commit .env.local, provider tokens, API keys, database URLs, or screenshots containing secrets.	Copy .env.example to .env.local, add local secrets there, and keep Windows User env vars outside the repo for Codex-only keys.
GitHub	Product Engineer	GitHub stores app source and review history, not runtime secrets.	Do not place secrets in commits, pull requests, issues, logs, exported packets, or public repo settings.	Use GitHub Actions secrets only for approved CI needs and keep the repo private until public release approval exists.
Vercel	AI SRE / Platform Engineer	Runtime secrets live in Vercel Environment Variables with Production, Preview, and Development scopes.	Do not put secrets in NEXT_PUBLIC_ variables or enable PUBLIC_PROOF_ENABLED before VAL-232 passes.	Use vercel env add for secrets, vercel env pull .env.local --yes for local sync, and keep SYNC_WRITEBACK_ENABLED=false until approval.
Rotation / leak response	OS Owner / AI Ops Lead	Any exposed secret is treated as compromised even if the exposed surface is later deleted.	Do not paste secret values into Linear, Notion, GitHub comments, screenshots, support tickets, or public proof packets.	Revoke, replace, update local/Vercel/CI storage, run validation, and record the rotation without exposing the value.

App Analytics Policy

Event	Surface	Allowed Payload	Forbidden Payload	Purpose
page_view	Vercel Web Analytics	Default Vercel page-view telemetry only.	No secrets, client names, claim text, Linear issue bodies, Notion content, export payloads, or user-entered data.	Understand which operator surfaces are used.
markdown_export_copy	Markdown Export	Event name only.	No exported Markdown text, selected record contents, client names, proof claims, or API keys.	Measure whether operators copy canonical Markdown exports.
markdown_export_download	Markdown Export	Event name only.	No filename content beyond the static event name and no exported Markdown body.	Measure whether operators download canonical Markdown exports.
backup_export_copy	Backup / Export	Event name only.	No JSON backup body, source map content, client records, or secret values.	Measure whether operators copy backup JSON.
backup_export_download	Backup / Export	Event name only.	No JSON backup body, source map content, client records, or secret values.	Measure whether operators download backup JSON.

Monitoring / Logging

Signal	Capture Point	Severity	Route	Safe Payload	Forbidden Payload
app_error	Global app error boundary and internal monitoring event API	Blocking when it breaks an operator path; review otherwise.	Vercel runtime logs, Linear evidence comment, Notion source map when tied to a foundation task.	Event type, route or surface, sanitized error summary, deployment target, commit SHA, and request ID when present.	No secrets, API tokens, client/source bodies, claim text, exported content, raw stack traces, or personal data.
failed_import	Importer failure handling and sync run log	Blocking when source truth cannot be loaded; review when a non-critical source is skipped.	Sync run record, failed import report, Notion cleanup or Linear reconciliation queue.	Source system, failure kind, affected record count, retry option, and reconciliation state.	No imported page bodies, issue descriptions, credential fragments, client names, or private URLs beyond approved source links.
sync_issue	Sync log reconciliation result	Blocking when writeback, contradiction, or source drift can change operator truth.	Sync run record, contradiction detector, Linear mutation draft if a status change is proposed.	Source system, status, read/write counts, conflict count, reconciliation status, and source title when already approved for internal use.	No unapproved writeback payloads, raw diff bodies, hidden source text, or mutation execution without approval.
app_health	GET /api/health and deployment inspection	Blocking when production is down or protected paths fail outside expected auth-offline mode.	Vercel deployment status, Command Center monitoring panel, Linear implementation comment.	App name, environment label, health status, current hard gates, auth mode, public proof lock, and timestamp.	No environment variable values, user session data, provider secrets, proof claims, or source document contents.

Health Check	Target	Expected State	Owner	Escalation
Production root	https://valdris-ai-team-os.vercel.app	200 OK and Command Center shell renders.	AI SRE / Platform Engineer	Create or update the active deployment issue with Vercel inspect link and rollback path.
Protected app route	/app	Authenticated app shell when Clerk is configured; 503 Auth env offline when Clerk env is intentionally absent.	AI SRE / Platform Engineer	Do not call this an app failure while Clerk env is intentionally offline; record it as auth dependency state.
Source import run	Notion, Linear, Markdown, GitHub importers	Every run emits sync status, read/write counts, reconciliation status, and failed import classification.	OS Owner / AI Ops Lead	Route failed source truth to the cleanup or reconciliation queue before any operator-facing claim changes.
Public proof lock	PUBLIC_PROOF_ENABLED and proof surfaces	Public proof remains disabled until VAL-232 passes with approved public-safe language.	Founder / CEO Boundary	Stop publication, revert unsafe copy, and record the claim violation under VAL-232.

Markdown Export

Source Surface

Command Center

Boundary

Internal operator export. No public proof claims before VAL-232.

---
title: Current Truth
system: Valdris.ai Foundation
source_surface: Command Center
source_data: src/modules/foundation/data.ts
linear_control: VAL-703
boundary: Internal operator export. No public proof claims before VAL-232.
---

# Current Truth

## Source Metadata
- Source surface: Command Center
- Source data: src/modules/foundation/data.ts
- Linear control: VAL-703
- Export boundary: Internal operator export. No public proof claims before VAL-232.

## Current Truth
| Issue | Status | Detail |
| --- | --- | --- |
| VAL-250 | Scaffold only | Core asset kit exists. It is not install-ready proof. |
| VAL-249 | Blocked | Do not unblock until independent operator proof passes. |
| VAL-464 | Not passed | Independent operator test is still an active proof gate. |
| VAL-478 | Next action | Tester selection is the next real proof-path action. |
| VAL-232 | Public claims blocker | No public proof claims until this passes. |

Backup / Export

Backup Scope

Hard truth, proof gates, proof status, blocker state, operator views, and protected do-not-touch surfaces.

Boundary

Internal backup only. Does not publish proof or change Linear/Notion state.

{
  "backupId": "critical-operating-data",
  "backupLabel": "Critical Operating Data",
  "system": "Valdris.ai Foundation",
  "sourceControl": "VAL-704",
  "boundary": "Internal backup only. Does not publish proof or change Linear/Notion state.",
  "sourceGeneratedFrom": "src/modules/foundation/data.ts",
  "records": {
    "currentTruth": [
      {
        "key": "VAL-250",
        "status": "Scaffold only",
        "detail": "Core asset kit exists. It is not install-ready proof.",
        "tone": "amber"
      },
      {
        "key": "VAL-249",
        "status": "Blocked",
        "detail": "Do not unblock until independent operator proof passes.",
        "tone": "red"
      },
      {
        "key": "VAL-464",
        "status": "Not passed",
        "detail": "Independent operator test is still an active proof gate.",
        "tone": "red"
      },
      {
        "key": "VAL-478",
        "status": "Next action",
        "detail": "Tester selection is the next real proof-path action.",
        "tone": "sky"
      },
      {
        "key": "VAL-232",
        "status": "Public claims blocker",
        "detail": "No public proof claims until this passes.",
        "tone": "red"
      }
    ],
    "commandCenterNextAction": {
      "issue": "VAL-478",
      "title": "Select independent operator tester",
      "owner": "OS Owner / AI Ops Lead",
      "state": "Next proof-path action",
      "why": "VAL-464 cannot run, and VAL-249 cannot unblock, until an independent tester is selected through VAL-478.",
      "outcome": "A tester is selected, given the install surface, and assigned the independent operator run."
    },
    "commandCenterBlockers": [
      {
        "issue": "VAL-232",
        "title": "Public proof claims blocked",
        "blockedSurface": "Website proof, case studies, public metrics, install-ready claims",
        "owner": "Founder / CEO Boundary",
        "source": "Current truth / proof gate policy",
        "age": "Open until proof bank is approved",
        "resolution": "Classify and approve proof claims before publishing.",
        "severity": "Blocking"
      },
      {
        "issue": "VAL-249",
        "title": "Install readiness blocked",
        "blockedSurface": "Install-ready status and operator handoff claims",
        "owner": "Client Delivery Systems Lead",
        "source": "Current truth / install gate",
        "age": "Open until independent operator proof passes",
        "resolution": "Keep blocked until independent operator proof passes.",
        "severity": "Blocking"
      },
      {
        "issue": "VAL-464",
        "title": "Independent operator test not passed",
        "blockedSurface": "VAL-249 unblock path",
        "owner": "Quality Enablement Lead",
        "source": "Current truth / independent operator test",
        "age": "Open until a pass result is recorded",
        "resolution": "Prepare and run the independent operator test after VAL-478.",
        "severity": "Blocking"
      }
    ],
    "activeProofGates": [
      {
        "gate": "VAL-478",
        "owner": "OS Owner / AI Ops Lead",
        "state": "Next action",
        "blocker": "Tester not selected",
        "evidence": "Current proof path starts here.",
        "nextAction": "Choose the independent tester and run setup."
      },
      {
        "gate": "VAL-464",
        "owner": "Quality Enablement Lead",
        "state": "Not passed",
        "blocker": "Independent operator proof has not passed",
        "evidence": "No pass result is recorded.",
        "nextAction": "Prepare the test after tester selection."
      },
      {
        "gate": "VAL-249",
        "owner": "Client Delivery Systems Lead",
        "state": "Blocked",
        "blocker": "Depends on VAL-464",
        "evidence": "Install-ready status is not approved.",
        "nextAction": "Do not unblock until VAL-464 passes."
      },
      {
        "gate": "VAL-232",
        "owner": "Founder / CEO Boundary",
        "state": "Blocked",
        "blocker": "Public claims are not approved",
        "evidence": "No public proof claims are allowed.",
        "nextAction": "Keep public proof surfaces gated."
      }
    ],
    "proofStatusPanel": [
      {
        "gate": "VAL-478",
        "claimSurface": "Tester selection is the next proof-path action",
        "evidence": "No selected independent operator is recorded.",
        "approvalState": "Open / next action",
        "publicUseBoundary": "Internal routing only. Do not present as operator proof."
      },
      {
        "gate": "VAL-464",
        "claimSurface": "Independent operator can run the install surface",
        "evidence": "No pass result is recorded.",
        "approvalState": "Not passed",
        "publicUseBoundary": "No public use. This must pass before install-ready language."
      },
      {
        "gate": "VAL-249",
        "claimSurface": "Install-ready operator handoff is approved",
        "evidence": "Blocked until independent operator proof passes.",
        "approvalState": "Blocked",
        "publicUseBoundary": "No install-ready claim until VAL-464 passes."
      },
      {
        "gate": "VAL-232",
        "claimSurface": "Website proof, case studies, public metrics, client claims",
        "evidence": "Public proof claims are not approved.",
        "approvalState": "Blocked",
        "publicUseBoundary": "No public proof claims before VAL-232 passes."
      },
      {
        "gate": "VAL-250",
        "claimSurface": "Core asset kit exists",
        "evidence": "Scaffold and core assets exist.",
        "approvalState": "Scaffold-complete only",
        "publicUseBoundary": "Internal source asset only. Do not use as install-ready proof."
      }
    ],
    "proofCenterView": [
      {
        "surface": "Tester selection",
        "gate": "VAL-478",
        "state": "Next action",
        "evidenceState": "No selected independent operator is recorded.",
        "allowedUse": "Internal proof-path routing only.",
        "nextAction": "Select the independent operator tester and assign the run path."
      },
      {
        "surface": "Independent operator proof",
        "gate": "VAL-464",
        "state": "Not passed",
        "evidenceState": "No pass result is recorded.",
        "allowedUse": "Internal QA and remediation only. No install-ready claim.",
        "nextAction": "Prepare and run the test after VAL-478 selects the tester."
      },
      {
        "surface": "Install readiness",
        "gate": "VAL-249",
        "state": "Blocked",
        "evidenceState": "Blocked until independent operator proof passes.",
        "allowedUse": "Internal delivery planning only.",
        "nextAction": "Keep blocked until VAL-464 passes."
      },
      {
        "surface": "Public proof claims",
        "gate": "VAL-232",
        "state": "Blocked",
        "evidenceState": "Public claim bank is not approved.",
        "allowedUse": "No website proof, case study, public metric, client claim, or public-ready wording.",
        "nextAction": "Classify claims and approve language before publishing."
      },
      {
        "surface": "Core asset kit",
        "gate": "VAL-250",
        "state": "Scaffold-complete only",
        "evidenceState": "Core assets exist, but install-ready proof is not approved.",
        "allowedUse": "Internal source artifact and build reference only.",
        "nextAction": "Do not use scaffold existence as proof of install readiness."
      },
      {
        "surface": "Sales-call proof language",
        "gate": "VAL-232",
        "state": "Controlled",
        "evidenceState": "Sales-call-only wording requires claim classification.",
        "allowedUse": "Only approved, non-public language after claim review.",
        "nextAction": "Route proposed language through Claim Approval before use."
      }
    ],
    "doNotTouchView": [
      {
        "protectedItem": "VAL-232",
        "sourceGate": "Public proof lock",
        "severity": "Hard block",
        "prohibitedAction": "Do not publish website proof, case studies, public metrics, client claims, or public-ready claim language.",
        "allowedPath": "Draft internal claim classifications and route language through Claim Approval.",
        "owner": "Founder / CEO Boundary",
        "releaseCondition": "VAL-232 passes with approved public-safe language."
      },
      {
        "protectedItem": "VAL-249",
        "sourceGate": "Install readiness lock",
        "severity": "Hard block",
        "prohibitedAction": "Do not unblock, close, or call the system install-ready before independent operator proof passes.",
        "allowedPath": "Keep blocked, collect evidence, and wait for VAL-464 decision.",
        "owner": "Client Delivery Systems Lead",
        "releaseCondition": "VAL-464 records a valid pass result with sufficient evidence."
      },
      {
        "protectedItem": "VAL-464",
        "sourceGate": "Proof gate lock",
        "severity": "Hard block",
        "prohibitedAction": "Do not mark passed from docs, app UI, scaffold completion, or partial test success.",
        "allowedPath": "Run the mock operator sequence and attach evidence from VAL-478 and VAL-470 through VAL-477.",
        "owner": "Quality Enablement Lead",
        "releaseCondition": "Full test run is scored as pass, fail, or pass with caveats."
      },
      {
        "protectedItem": "VAL-478",
        "sourceGate": "Next-action lock",
        "severity": "Blocking",
        "prohibitedAction": "Do not bury, skip, or replace tester selection with downstream proof tasks.",
        "allowedPath": "Select the independent operator tester and record assignment evidence.",
        "owner": "OS Owner / AI Ops Lead",
        "releaseCondition": "Tester is selected, access boundary is recorded, and the run packet is assigned."
      },
      {
        "protectedItem": "VAL-250",
        "sourceGate": "Claim boundary",
        "severity": "Blocking",
        "prohibitedAction": "Do not relabel scaffold/core-asset completion as install-ready proof.",
        "allowedPath": "Reference as scaffold-complete only and link to active proof gates.",
        "owner": "Product Engineer",
        "releaseCondition": "Independent proof path passes and readiness is separately approved."
      },
      {
        "protectedItem": "Live Notion operator pages",
        "sourceGate": "Operator interface lock",
        "severity": "Blocking",
        "prohibitedAction": "Do not move, archive, replace, or bury AI Team OS home, 00 Command Center, or Operator Index.",
        "allowedPath": "Update live links and source maps through approval-controlled edits.",
        "owner": "OS Owner / AI Ops Lead",
        "releaseCondition": "Nick approves a replacement operator interface and source map."
      },
      {
        "protectedItem": "Source/history pages",
        "sourceGate": "No-delete lock",
        "severity": "Blocking",
        "prohibitedAction": "Do not delete reconstruction notes, older handoffs, duplicate drafts, or historical source artifacts.",
        "allowedPath": "Park, link, source-map, and extract useful canon after approval.",
        "owner": "OS Owner / AI Ops Lead",
        "releaseCondition": "Source is extracted, linked, parked, and approved."
      },
      {
        "protectedItem": "Utari/client-specific artifacts",
        "sourceGate": "Client boundary",
        "severity": "Hard block",
        "prohibitedAction": "Do not merge client-specific evidence into Valdris company canon or public proof.",
        "allowedPath": "Keep inside the matching client instance or extract only approved reusable patterns.",
        "owner": "Client Delivery Systems Lead",
        "releaseCondition": "Reusable pattern is approved and client-specific evidence is removed."
      },
      {
        "protectedItem": "Linear Done transitions",
        "sourceGate": "Approval row lock",
        "severity": "Blocking",
        "prohibitedAction": "Do not move implementation issues to Done while the matching approval row is open.",
        "allowedPath": "Move to In Progress with implementation comment and wait for approval.",
        "owner": "OS Owner / AI Ops Lead",
        "releaseCondition": "Approval row is answered and locked."
      },
      {
        "protectedItem": "Linear issue clusters marked for reconciliation",
        "sourceGate": "No-silent-mutation lock",
        "severity": "Blocking",
        "prohibitedAction": "Do not close, cancel, relabel, or merge older issues without a source map and replacement link.",
        "allowedPath": "Draft mutation recommendations in Notion and wait for approval.",
        "owner": "OS Owner / AI Ops Lead",
        "releaseCondition": "Replacement issue, source map, and approval row are linked."
      },
      {
        "protectedItem": "Public website/proof surfaces",
        "sourceGate": "VAL-232 publication lock",
        "severity": "Hard block",
        "prohibitedAction": "Do not ship proof page, case studies, client logos, metrics, or install-ready language to the website.",
        "allowedPath": "Keep website proof content draft/internal and route every claim through Proof Center.",
        "owner": "Founder / CEO Boundary",
        "releaseCondition": "VAL-232 approves public-safe claim language before deploy."
      },
      {
        "protectedItem": "Approval Log / Linear Mutation Drafts",
        "sourceGate": "Approval workflow lock",
        "severity": "Blocking",
        "prohibitedAction": "Do not bypass approval rows, mutation drafts, or source maps for status changes and canon moves.",
        "allowedPath": "Create the approval row, source map, and mutation draft, then wait for the approval answer.",
        "owner": "OS Owner / AI Ops Lead",
        "releaseCondition": "Approval row is answered, locked, and linked to the mutation evidence."
      }
    ],
    "environmentSecretsPolicy": [
      {
        "area": "Local development",
        "owner": "AI SRE / Platform Engineer",
        "requiredControl": ".env.example tracks safe variable names; .env.local holds real local values and remains gitignored.",
        "prohibitedAction": "Do not commit .env.local, provider tokens, API keys, database URLs, or screenshots containing secrets.",
        "operatingAction": "Copy .env.example to .env.local, add local secrets there, and keep Windows User env vars outside the repo for Codex-only keys."
      },
      {
        "area": "GitHub",
        "owner": "Product Engineer",
        "requiredControl": "GitHub stores app source and review history, not runtime secrets.",
        "prohibitedAction": "Do not place secrets in commits, pull requests, issues, logs, exported packets, or public repo settings.",
        "operatingAction": "Use GitHub Actions secrets only for approved CI needs and keep the repo private until public release approval exists."
      },
      {
        "area": "Vercel",
        "owner": "AI SRE / Platform Engineer",
        "requiredControl": "Runtime secrets live in Vercel Environment Variables with Production, Preview, and Development scopes.",
        "prohibitedAction": "Do not put secrets in NEXT_PUBLIC_ variables or enable PUBLIC_PROOF_ENABLED before VAL-232 passes.",
        "operatingAction": "Use vercel env add for secrets, vercel env pull .env.local --yes for local sync, and keep SYNC_WRITEBACK_ENABLED=false until approval."
      },
      {
        "area": "Rotation / leak response",
        "owner": "OS Owner / AI Ops Lead",
        "requiredControl": "Any exposed secret is treated as compromised even if the exposed surface is later deleted.",
        "prohibitedAction": "Do not paste secret values into Linear, Notion, GitHub comments, screenshots, support tickets, or public proof packets.",
        "operatingAction": "Revoke, replace, update local/Vercel/CI storage, run validation, and record the rotation without exposing the value."
      }
    ],
    "appAnalyticsPolicy": [
      {
        "event": "page_view",
        "surface": "Vercel Web Analytics",
        "allowedPayload": "Default Vercel page-view telemetry only.",
        "forbiddenPayload": "No secrets, client names, claim text, Linear issue bodies, Notion content, export payloads, or user-entered data.",
        "purpose": "Understand which operator surfaces are used."
      },
      {
        "event": "markdown_export_copy",
        "surface": "Markdown Export",
        "allowedPayload": "Event name only.",
        "forbiddenPayload": "No exported Markdown text, selected record contents, client names, proof claims, or API keys.",
        "purpose": "Measure whether operators copy canonical Markdown exports."
      },
      {
        "event": "markdown_export_download",
        "surface": "Markdown Export",
        "allowedPayload": "Event name only.",
        "forbiddenPayload": "No filename content beyond the static event name and no exported Markdown body.",
        "purpose": "Measure whether operators download canonical Markdown exports."
      },
      {
        "event": "backup_export_copy",
        "surface": "Backup / Export",
        "allowedPayload": "Event name only.",
        "forbiddenPayload": "No JSON backup body, source map content, client records, or secret values.",
        "purpose": "Measure whether operators copy backup JSON."
      },
      {
        "event": "backup_export_download",
        "surface": "Backup / Export",
        "allowedPayload": "Event name only.",
        "forbiddenPayload": "No JSON backup body, source map content, client records, or secret values.",
        "purpose": "Measure whether operators download backup JSON."
      }
    ],
    "monitoringLoggingPolicy": [
      {
        "signal": "app_error",
        "capturePoint": "Global app error boundary and internal monitoring event API",
        "severity": "Blocking when it breaks an operator path; review otherwise.",
        "routedTo": "Vercel runtime logs, Linear evidence comment, Notion source map when tied to a foundation task.",
        "safePayload": "Event type, route or surface, sanitized error summary, deployment target, commit SHA, and request ID when present.",
        "forbiddenPayload": "No secrets, API tokens, client/source bodies, claim text, exported content, raw stack traces, or personal data."
      },
      {
        "signal": "failed_import",
        "capturePoint": "Importer failure handling and sync run log",
        "severity": "Blocking when source truth cannot be loaded; review when a non-critical source is skipped.",
        "routedTo": "Sync run record, failed import report, Notion cleanup or Linear reconciliation queue.",
        "safePayload": "Source system, failure kind, affected record count, retry option, and reconciliation state.",
        "forbiddenPayload": "No imported page bodies, issue descriptions, credential fragments, client names, or private URLs beyond approved source links."
      },
      {
        "signal": "sync_issue",
        "capturePoint": "Sync log reconciliation result",
        "severity": "Blocking when writeback, contradiction, or source drift can change operator truth.",
        "routedTo": "Sync run record, contradiction detector, Linear mutation draft if a status change is proposed.",
        "safePayload": "Source system, status, read/write counts, conflict count, reconciliation status, and source title when already approved for internal use.",
        "forbiddenPayload": "No unapproved writeback payloads, raw diff bodies, hidden source text, or mutation execution without approval."
      },
      {
        "signal": "app_health",
        "capturePoint": "GET /api/health and deployment inspection",
        "severity": "Blocking when production is down or protected paths fail outside expected auth-offline mode.",
        "routedTo": "Vercel deployment status, Command Center monitoring panel, Linear implementation comment.",
        "safePayload": "App name, environment label, health status, current hard gates, auth mode, public proof lock, and timestamp.",
        "forbiddenPayload": "No environment variable values, user session data, provider secrets, proof claims, or source document contents."
      }
    ],
    "monitoringHealthChecks": [
      {
        "check": "Production root",
        "target": "https://valdris-ai-team-os.vercel.app",
        "expected": "200 OK and Command Center shell renders.",
        "owner": "AI SRE / Platform Engineer",
        "escalation": "Create or update the active deployment issue with Vercel inspect link and rollback path."
      },
      {
        "check": "Protected app route",
        "target": "/app",
        "expected": "Authenticated app shell when Clerk is configured; 503 Auth env offline when Clerk env is intentionally absent.",
        "owner": "AI SRE / Platform Engineer",
        "escalation": "Do not call this an app failure while Clerk env is intentionally offline; record it as auth dependency state."
      },
      {
        "check": "Source import run",
        "target": "Notion, Linear, Markdown, GitHub importers",
        "expected": "Every run emits sync status, read/write counts, reconciliation status, and failed import classification.",
        "owner": "OS Owner / AI Ops Lead",
        "escalation": "Route failed source truth to the cleanup or reconciliation queue before any operator-facing claim changes."
      },
      {
        "check": "Public proof lock",
        "target": "PUBLIC_PROOF_ENABLED and proof surfaces",
        "expected": "Public proof remains disabled until VAL-232 passes with approved public-safe language.",
        "owner": "Founder / CEO Boundary",
        "escalation": "Stop publication, revert unsafe copy, and record the claim violation under VAL-232."
      }
    ],
    "valdrisSeedBatch": {
      "id": "valdris-foundation-seed-2026-05-21",
      "instance": "Valdris",
      "sourceControl": "VAL-710",
      "importedAt": "2026-05-21",
      "status": "Review",
      "boundary": "Internal operator seed only. This does not prove install readiness or public claims."
    },
    "valdrisSeedSources": [
      {
        "system": "Notion",
        "record": "AI Team OS home",
        "role": "Workspace root, canonical navigation, current proof path, source/history boundary.",
        "url": "https://www.notion.so/34ddbdcf654981028f3bd33f387bfe51",
        "approvedUse": "Operator root and navigation source."
      },
      {
        "system": "Notion",
        "record": "00 Command Center",
        "role": "First landing page for status, blockers, next action, and operating traceability.",
        "url": "https://www.notion.so/356dbdcf654981ae862ccfb1024c2c67",
        "approvedUse": "Current command surface."
      },
      {
        "system": "Notion",
        "record": "AI Team OS Operator Index v1.0",
        "role": "Candidate operator interface for independent operator testing.",
        "url": "https://www.notion.so/35edbdcf654981709dbdefcf2ade4437",
        "approvedUse": "Navigation and operator test surface only. Independent proof has not passed."
      },
      {
        "system": "Notion",
        "record": "03 Foundation / Primitives",
        "role": "Foundation rules, primitives, source maps, and approval-linked records.",
        "url": "https://www.notion.so/356dbdcf654981618855e7a86e4fcfbe",
        "approvedUse": "Foundation source-map parent and rule reference."
      },
      {
        "system": "Linear",
        "record": "VAL-710",
        "role": "Execution control for seeding Valdris operating data into the app.",
        "url": "https://linear.app/valdris/issue/VAL-710/214-seed-app-with-valdris-data",
        "approvedUse": "Task control and status trail."
      },
      {
        "system": "GitHub",
        "record": "nickcarmonadigital/valdris-ai-team-os",
        "role": "Private application source and implementation history.",
        "url": "https://github.com/nickcarmonadigital/valdris-ai-team-os",
        "approvedUse": "App source and validation evidence."
      },
      {
        "system": "Vercel",
        "record": "valdris-ai-team-os production deployment",
        "role": "Production deployment target for the operator command center.",
        "url": "https://valdris-ai-team-os.vercel.app",
        "approvedUse": "Runtime availability evidence only."
      }
    ],
    "valdrisOperatingSeed": [
      {
        "area": "Operator root",
        "seededData": "AI Team OS is the main Valdris operating-system workspace. Linear tracks the work, Notion holds durable outputs, and Markdown remains the AI-readable backup.",
        "sourceRecord": "AI Team OS home",
        "sourceUrl": "https://www.notion.so/34ddbdcf654981028f3bd33f387bfe51",
        "operatorUse": "Start here to locate the live command surface, source areas, install system, offer/proof area, and archive.",
        "boundary": "Do not treat source/history pages as live operator instructions unless the Command Center or Operator Index routes there."
      },
      {
        "area": "Command surface",
        "seededData": "00 Command Center is the first place to land when checking status, next action, blockers, and operating traceability.",
        "sourceRecord": "00 Command Center",
        "sourceUrl": "https://www.notion.so/356dbdcf654981ae862ccfb1024c2c67",
        "operatorUse": "Use it before touching Notion moves, Linear status, proof gates, install assets, or public claims.",
        "boundary": "If another artifact conflicts with the current truth freeze, the current truth freeze wins."
      },
      {
        "area": "Current proof path",
        "seededData": "VAL-478 -> VAL-464 -> VAL-470 through VAL-477 -> VAL-249 decision.",
        "sourceRecord": "AI Team OS home / 00 Command Center",
        "sourceUrl": "https://www.notion.so/34ddbdcf654981028f3bd33f387bfe51",
        "operatorUse": "Use this sequence to route independent operator proof work.",
        "boundary": "Do not unblock VAL-249 before VAL-464 records a valid pass result."
      },
      {
        "area": "Public proof lock",
        "seededData": "VAL-232 -> approved claim language -> website / sales assets.",
        "sourceRecord": "AI Team OS home / 00 Command Center",
        "sourceUrl": "https://linear.app/valdris/issue/VAL-232/offer-verify-proof-claims-bank-for-safe-sales-use",
        "operatorUse": "Route every public claim, case study, proof page, and metric through VAL-232.",
        "boundary": "No public proof claims, install-ready claims, case studies, client logos, or metrics before VAL-232 passes."
      },
      {
        "area": "Operator interface",
        "seededData": "AI Team OS Operator Index v1.0 is the candidate front door for independent operator testing.",
        "sourceRecord": "AI Team OS Operator Index v1.0",
        "sourceUrl": "https://www.notion.so/35edbdcf654981709dbdefcf2ade4437",
        "operatorUse": "Use as the testable navigation surface after the Command Center status check.",
        "boundary": "Candidate interface only. Independent operator proof has not passed."
      },
      {
        "area": "Department OS set",
        "seededData": "Delivery OS, Product OS, Engineering OS, Platform OS, QA / Training OS, RevOps OS, People / Ops / Admin OS, and CEO Pulse.",
        "sourceRecord": "Operator Index / Department Operating Manuals",
        "sourceUrl": "https://www.notion.so/35edbdcf65498118b876da8d55cb30ed",
        "operatorUse": "Use as the top-level company operating map for role and workflow routing.",
        "boundary": "Manual existence is source structure, not install-ready proof."
      },
      {
        "area": "Role manual set",
        "seededData": "Client Delivery Systems Lead, AI Product Operator, Product Engineer, AI SRE / Platform Engineer, Quality Enablement Lead, Revenue Systems Operator, OS Owner / AI Ops Lead, and Founder / CEO Boundary.",
        "sourceRecord": "Operator Index / Role Operating Manuals",
        "sourceUrl": "https://www.notion.so/35edbdcf6549813daa15e1d58500d992",
        "operatorUse": "Route work through role ownership, handoff, escalation, and approval boundaries.",
        "boundary": "No role can approve proof claims or install readiness outside its gate."
      },
      {
        "area": "Workflow routes",
        "seededData": "VS-002 onboarding / first value, VS-003 request / build, VS-004 change / incident, VS-005 proof / pulse, weekly OS review, and tool/source request.",
        "sourceRecord": "AI Team OS Operator Index v1.0",
        "sourceUrl": "https://www.notion.so/35edbdcf654981709dbdefcf2ade4437",
        "operatorUse": "Use route IDs to assign agents, prompts, SOPs, outputs, gates, and handoffs.",
        "boundary": "Agents must not start from generic prompts; they must operate from route, role, task, and gate context."
      },
      {
        "area": "Source/history boundary",
        "seededData": "01 Source Evidence, 02 Source Synthesis, reconstruction reports, legacy phase notes, and 99 Archive are source/history unless explicitly routed by the Command Center or Operator Index.",
        "sourceRecord": "AI Team OS home",
        "sourceUrl": "https://www.notion.so/34ddbdcf654981028f3bd33f387bfe51",
        "operatorUse": "Use source/history for rationale, extraction, and traceability.",
        "boundary": "Source/history does not override current Notion and Linear truth."
      },
      {
        "area": "App deployment",
        "seededData": "Production command center is deployed at valdris-ai-team-os.vercel.app with health checks and monitoring/logging surfaced.",
        "sourceRecord": "VAL-706 / VAL-708 source maps",
        "sourceUrl": "https://www.notion.so/367dbdcf65498174a294fb04a2f8cb31",
        "operatorUse": "Use production runtime only as app availability evidence.",
        "boundary": "Deployment proves app availability, not install readiness or public proof."
      },
      {
        "area": "App test coverage",
        "seededData": "App validation covers core data model, import mappers, contradiction detection, operator views, monitoring/logging, and health endpoint.",
        "sourceRecord": "VAL-709 source map",
        "sourceUrl": "https://www.notion.so/367dbdcf654981e0b3b9c892efb06ec5",
        "operatorUse": "Use as app implementation coverage evidence for foundation execution.",
        "boundary": "Tests prove coverage only. They do not pass VAL-464 or unblock VAL-249."
      }
    ],
    "utariSeedBatch": {
      "id": "utari-pilot-seed-2026-05-21",
      "instanceId": "UTARI-PILOT-2026",
      "instanceName": "Utari Pilot / Source Instance",
      "sourceControl": "VAL-711",
      "importedAt": "2026-05-21",
      "status": "Review",
      "boundary": "Separated pilot/source seed only. Do not merge into Valdris company canon, public proof, or install readiness."
    },
    "utariSeedSources": [
      {
        "system": "Notion",
        "record": "VAL-637 Utari Operating Instance Separation",
        "role": "Current Utari instance boundary standard and source classification rule.",
        "url": "https://www.notion.so/367dbdcf654981fcb6f1f2e10d5bcd6f",
        "approvedUse": "Utari boundary source. Approval row remains open."
      },
      {
        "system": "Notion",
        "record": "VAL-637 Approval Row",
        "role": "Approval control for the Utari boundary standard.",
        "url": "https://www.notion.so/367dbdcf65498133bc47c9ac9aac284a",
        "approvedUse": "Review-state control. Not a Done or public-use approval."
      },
      {
        "system": "Notion",
        "record": "VAL-636 Valdris Operating Instance Separation",
        "role": "Separates Valdris company OS from Utari pilot/source material.",
        "url": "https://www.notion.so/367dbdcf6549811cb677c15c38a11b4c",
        "approvedUse": "Cross-instance boundary reference."
      },
      {
        "system": "Notion",
        "record": "VAL-662 App Instance Model",
        "role": "Defines app instance types, required fields, and data isolation rules.",
        "url": "https://www.notion.so/367dbdcf6549817a91cfd71c1bd0a35f",
        "approvedUse": "App instance model reference."
      },
      {
        "system": "Linear",
        "record": "VAL-711",
        "role": "Execution control for seeding Utari data into the app.",
        "url": "https://linear.app/valdris/issue/VAL-711/215-seed-app-with-utari-data",
        "approvedUse": "Task control and status trail."
      }
    ],
    "utariOperatingSeed": [
      {
        "area": "Instance identity",
        "seededData": "UTARI-PILOT-2026 is the canonical identifier for the Utari Pilot / Source Instance.",
        "sourceRecord": "VAL-637 Utari Operating Instance Separation",
        "sourceUrl": "https://www.notion.so/367dbdcf654981fcb6f1f2e10d5bcd6f",
        "operatorUse": "Use this ID when routing Utari pilot/source material, source maps, proof records, and reusable lesson candidates.",
        "boundary": "This creates an app seed boundary only. It does not create a live client shell or public case study."
      },
      {
        "area": "Instance classification",
        "seededData": "Utari is classified as Pilot Source / History / Internal Evidence with Internal Only proof default.",
        "sourceRecord": "VAL-637 Utari Operating Instance Separation",
        "sourceUrl": "https://www.notion.so/367dbdcf654981fcb6f1f2e10d5bcd6f",
        "operatorUse": "Use Utari records for internal lessons, replay evidence, and source classification.",
        "boundary": "Do not treat Utari as Valdris company ownership, generic install readiness, or future-client default."
      },
      {
        "area": "Allowed contents",
        "seededData": "Utari pilot runbook, validation, retro ADR, minimum operating spine lessons, handoff examples, workflow replays, and source-of-truth gaps.",
        "sourceRecord": "VAL-637 Utari Operating Instance Separation",
        "sourceUrl": "https://www.notion.so/367dbdcf654981fcb6f1f2e10d5bcd6f",
        "operatorUse": "Keep these records in the Utari instance unless a current Linear issue routes a reusable extraction.",
        "boundary": "Do not copy raw client/private material into the Valdris company seed or public surface."
      },
      {
        "area": "Excluded contents",
        "seededData": "Valdris company baseline ownership, generic Delivery OS install readiness, future-client assumptions, public case-study language, public proof claims, website copy, and Valdris legal/commercial terms.",
        "sourceRecord": "VAL-637 Utari Operating Instance Separation",
        "sourceUrl": "https://www.notion.so/367dbdcf654981fcb6f1f2e10d5bcd6f",
        "operatorUse": "Use this exclusion list before promoting any Utari-sourced pattern.",
        "boundary": "Do not promote Utari-specific facts into reusable doctrine without change control."
      },
      {
        "area": "Promotion rule",
        "seededData": "A reusable lesson can move into AI Team OS doctrine only when the source artifact is linked, classification is stated, Utari-specific facts are separated, a current Linear issue routes the promotion, and approval is linked.",
        "sourceRecord": "VAL-637 Utari Operating Instance Separation",
        "sourceUrl": "https://www.notion.so/367dbdcf654981fcb6f1f2e10d5bcd6f",
        "operatorUse": "Use this rule for any proposed pattern extracted from Utari.",
        "boundary": "Promotion does not clear VAL-232, VAL-464, or VAL-249."
      },
      {
        "area": "Public proof rule",
        "seededData": "Utari can support internal learning and internal proof classification only by default.",
        "sourceRecord": "VAL-637 Utari Operating Instance Separation",
        "sourceUrl": "https://www.notion.so/367dbdcf654981fcb6f1f2e10d5bcd6f",
        "operatorUse": "Route any named client reference, proof claim, screenshot, testimonial, metric, or case-study language through VAL-232.",
        "boundary": "No Utari public proof use without exact claim and surface approval."
      },
      {
        "area": "App instance model",
        "seededData": "Utari is a distinct app instance type with its own source roots, proof records, claim boundaries, archive rules, and data isolation.",
        "sourceRecord": "VAL-662 App Instance Model",
        "sourceUrl": "https://www.notion.so/367dbdcf6549817a91cfd71c1bd0a35f",
        "operatorUse": "Use the app instance model to keep Utari separate from Valdris, templates, and future client instances.",
        "boundary": "Proof and claim records are instance-scoped unless explicitly promoted through approval."
      }
    ],
    "truthValidationBatch": {
      "id": "truth-validation-2026-05-21",
      "sourceControl": "VAL-712",
      "validatedAt": "2026-05-21",
      "status": "Review",
      "scope": "Compare app hard truth against current Notion command surfaces and Linear proof-gate issue states.",
      "boundary": "Validation queues contradictions and guardrails. It does not pass VAL-464, unblock VAL-249, or approve public claims."
    },
    "truthValidationFindings": [
      {
        "subject": "VAL-250",
        "severity": "Blocking",
        "appTruth": "Scaffold only",
        "notionTruth": "Scaffold/core-asset-complete only; not install-ready proof.",
        "linearTruth": "Done",
        "decision": "Treat Linear Done as asset-kit completion only. Do not convert it into install-ready language.",
        "queuedAction": "Keep the app, Notion, and Linear comments explicit that VAL-250 is not install-ready proof."
      },
      {
        "subject": "VAL-249",
        "severity": "Blocking",
        "appTruth": "Blocked",
        "notionTruth": "Open and blocked until independent operator proof passes.",
        "linearTruth": "In Progress",
        "decision": "Treat the issue as active but blocked. Do not unblock or close it before VAL-464 records a pass.",
        "queuedAction": "Queue a Linear reconciliation comment that states blocked-by-VAL-464 without changing status to Done."
      },
      {
        "subject": "VAL-464",
        "severity": "Blocking",
        "appTruth": "Not passed",
        "notionTruth": "Independent operator test has not passed.",
        "linearTruth": "Todo",
        "decision": "No contradiction. Todo maps to not-run and not-passed for this gate.",
        "queuedAction": "Keep visible as the active proof gate after VAL-478 tester selection."
      },
      {
        "subject": "VAL-478",
        "severity": "Blocking",
        "appTruth": "Next action",
        "notionTruth": "Next real proof-path action.",
        "linearTruth": "Todo",
        "decision": "No contradiction. Todo means the next action is still unexecuted.",
        "queuedAction": "Keep top-of-command-center until tester, surface, schedule, and VAL-470 start decision are recorded."
      },
      {
        "subject": "VAL-232",
        "severity": "Blocking",
        "appTruth": "Public claims blocker",
        "notionTruth": "No public proof claims until VAL-232 passes.",
        "linearTruth": "Todo",
        "decision": "No contradiction. Todo preserves the public proof lock.",
        "queuedAction": "Keep website proof, case studies, client claims, public metrics, and install-ready public language locked."
      },
      {
        "subject": "Proof path sequence",
        "severity": "Review",
        "appTruth": "VAL-478 -> VAL-464 -> VAL-470 through VAL-477 -> VAL-249 decision",
        "notionTruth": "00 Command Center compresses the path as VAL-478 -> VAL-464 -> VAL-249; AI Team OS home expands the child tests.",
        "linearTruth": "VAL-470 through VAL-477 are queued proof-path children.",
        "decision": "Not a conflict. Use the expanded path in the app so operators see the test sequence.",
        "queuedAction": "Keep compressed and expanded paths source-mapped to avoid a second proof path."
      }
    ],
    "truthContradictionQueue": [
      {
        "item": "VAL-249 blocked-state mismatch",
        "severity": "Blocking",
        "queueState": "Queued",
        "sourceSystems": "App / Notion / Linear",
        "recommendedAction": "Preserve blocked interpretation; draft Linear comment linking VAL-249 to VAL-464 pass evidence.",
        "owner": "Client Delivery Systems Lead",
        "doNotCross": "Do not unblock, close, or call install-ready before VAL-464 passes."
      },
      {
        "item": "VAL-250 done-state interpretation risk",
        "severity": "Blocking",
        "queueState": "Queued",
        "sourceSystems": "App / Notion / Linear",
        "recommendedAction": "Preserve scaffold-only language everywhere VAL-250 appears.",
        "owner": "Product Engineer",
        "doNotCross": "Do not use Done as install-ready proof."
      },
      {
        "item": "Proof path compressed-versus-expanded wording",
        "severity": "Review",
        "queueState": "Mapped",
        "sourceSystems": "Notion / App / Linear",
        "recommendedAction": "Use the expanded sequence in operator UI and keep the compressed Command Center path as shorthand.",
        "owner": "Quality Enablement Lead",
        "doNotCross": "Do not create a parallel proof path outside VAL-478, VAL-464, and VAL-470 through VAL-477."
      }
    ],
    "truthValidationCleanChecks": [
      {
        "check": "VAL-464 status mapping",
        "result": "Clean",
        "evidence": "Linear Todo and app Not passed both mean no pass evidence is recorded."
      },
      {
        "check": "VAL-478 next-action mapping",
        "result": "Clean",
        "evidence": "Linear Todo and Notion next-action language both point to unfinished tester selection."
      },
      {
        "check": "VAL-232 public-proof lock",
        "result": "Clean",
        "evidence": "Linear Todo, Notion blocker language, and app lock all keep public proof disabled."
      }
    ],
    "initialOperatorViews": [
      "Command Center dashboard",
      "Active gates panel",
      "Blockers panel",
      "Proof status panel",
      "Valdris seed data panel",
      "Utari seed data panel",
      "Truth validation panel",
      "OS tree view",
      "SOP library",
      "SkillCard library",
      "KEEP / MERGE / CLOSE / PARK review table",
      "Source/history archive view",
      "Do-not-touch registry",
      "Markdown export panel",
      "Backup/export panel",
      "Environment/secrets policy panel",
      "App analytics policy panel",
      "Monitoring/logging panel"
    ]
  }
}

Scaffold Path

VAL-665

Build GitHub repo

In progress

VAL-667

Create database schema

Schema hardened

VAL-668

Create auth

Auth scaffolded

VAL-669

Create Nick-only admin

Policy scaffolded

VAL-670

Create permissions model

Model scaffolded

VAL-671

Create audit log

Audit scaffolded

VAL-672

Create Notion importer

Importer scaffolded

VAL-673

Create Linear importer

Importer scaffolded

VAL-674

Create Markdown importer

Importer scaffolded

VAL-675

Create GitHub reference importer

Importer scaffolded

VAL-676

Create sync logs

Sync log scaffolded

VAL-677

Create failed import handling

Failure handling scaffolded

VAL-678

Create contradiction detector

Detector scaffolded

VAL-679

Create Command Center dashboard

Dashboard surfaced

VAL-680

Create active gates panel

Panel surfaced

VAL-682

Create blockers panel

Panel surfaced

VAL-681

Create next action panel

Panel surfaced

VAL-683

Create proof status panel

Panel surfaced

VAL-684

Create client/install switcher

Switcher surfaced

VAL-685

Create OS tree view

Tree surfaced

VAL-686

Create Foundation view

View surfaced

VAL-687

Create Department view

View surfaced

VAL-688

Create Role view

View surfaced

VAL-689

Create Workflow Route view

View surfaced

VAL-690

Create SOP Library view

View surfaced

VAL-691

Create SkillCard Library view

View surfaced

VAL-692

Create Prompt Registry view

View surfaced

VAL-693

Create Handoff view

View surfaced

VAL-694

Create Proof Center

View surfaced

VAL-695

Create Install Packet generator

Generator surfaced

VAL-696

Create Mock Operator Test runner

Runner surfaced

VAL-697

Create KEEP / MERGE / CLOSE / PARK review table

Review table surfaced

VAL-698

Create Notion cleanup queue

Queue surfaced

VAL-699

Create Linear reconciliation queue

Queue surfaced

VAL-700

Create source/history archive view

Archive view surfaced

VAL-701

Create do-not-touch view

Guardrail view surfaced

VAL-702

Add Mermaid rendering in app

Diagram rendering surfaced

VAL-704

Add backup/export

Backup export surfaced

VAL-705

Add environment/secrets policy

Policy surfaced

VAL-707

Add app analytics

Analytics policy surfaced

VAL-708

Add app monitoring/logging

Monitoring/logging surfaced

VAL-710

Seed app with Valdris data

Source-linked seed surfaced

VAL-711

Seed app with Utari data

Separated seed surfaced

VAL-712

Validate app against current Notion/Linear truth

Truth validation surfaced

First Operator Views

01Command Center dashboard

02Active gates panel

03Blockers panel

04Proof status panel

05Valdris seed data panel

06Utari seed data panel

07Truth validation panel

08OS tree view

09SOP library

10SkillCard library

11KEEP / MERGE / CLOSE / PARK review table

12Source/history archive view

13Do-not-touch registry

14Markdown export panel

15Backup/export panel

16Environment/secrets policy panel

17App analytics policy panel

18Monitoring/logging panel

Source Boundaries

Source	Role	Write Policy
Notion	Live operating manual and approval log	Draft updates only until approval locks are answered.
Linear	Execution tracker and proof gate state	Status changes stay explicit and commented.
GitHub	Application source and deployment reference	Private repo first. No corpus dump.
Vercel	Preview and production deployment target	Deploy after repo validation and env policy.

Next controlled action: select the independent operator tester.VAL-478VAL-464