Bootstrap org workspace and align policy packet paths

.agents/policy/taylored-policy-rules.md

@@ -1,21 +1,20 @@
 <!-- GENERATED FILE. DO NOT EDIT HERE. -->
-<!-- CANONICAL SOURCE: bitpod-docs/process/taylored-policy-rules.md -->
+<!-- CANONICAL SOURCE: bitpod-docs/policies/taylored-policy-rules.md -->
 <!-- MIRROR ROLE: repo packet mirror -->
 # Taylored Policy Rules
 
-CANONICAL SOURCE: `bitpod-docs/process/taylored-policy-rules.md`
-LOCAL ROOT MIRROR: `$WORKSPACE/taylored-policy-rules.md` bootstrap mirror only
-EDIT SURFACE: edit this file first; generated mirrors must not become parallel canon
+CANONICAL SOURCE: `bitpod-docs/policies/taylored-policy-rules.md`
+EDIT SURFACE: edit this file first
 
 NAME: Taylored Policy Rules
 STATUS: Active
-DATE: 2026-03-24
-VERSION: 1.1
+DATE: 2026-04-05
+VERSION: 1.2
 OWNER: Workspace / Product Development
 DESCRIPTION: Enumerates prohibition IDs, enforcement states, alertability, and exception eligibility.
 SCOPE: Root prohibitions for the entire workspace.
-ENTRYPOINT: Referenced by repo `AGENTS.md` files and governance docs.
-DEPENDENCIES: `taylored-policy.md`, `../AGENTS.md`.
+ENTRYPOINT: Referenced by repo `AGENTS.md` files, root `AGENTS.md`, and governance docs.
+DEPENDENCIES: `taylored-policy.md`, `policy-registry.toml`, `../AGENTS.md`.
 OVERRIDE_POLICY: Only rules marked `exception_allowed = YES` may be declared as explicit repo exceptions.
 
 Status: Active shared policy rules file
@@ -75,11 +74,19 @@ Every exception must include:
 | `TPR-011` | GitHub-Native Minimalism | Do not rely on GitHub-native config as the main Taylor01 portability layer. | root governance | `DOCUMENTED_ONLY` | `NO_ALERT_YET` | `NO` | `taylored-policy.md` |
 | `TPR-012` | Tokenized Public Root | Do not publish person-specific local paths in root public policy surfaces. | root public docs | `ENFORCED` | `ALERT_ON_SUCCESS` | `YES` | `taylored-policy.md` |
 | `TPR-013` | Secretless Repo Trees | Do not store secrets in tracked repo files or shared handoff folders by default. | repo files and handoffs | `ENFORCED` | `ALERT_ON_SUCCESS` | `YES` | `taylored-policy.md` |
-| `TPR-014` | Root Policy Canon | Do not create, restore, or treat legacy policy shim files as the primary policy authoring surface once `taylored-policy.md` exists. | root policy files | `ENFORCED` | `ALERT_ON_SUCCESS` | `NO` | `taylored-policy.md` |
+| `TPR-014` | Root Policy Canon | Do not create, restore, or treat competing root policy files as the primary policy authoring surface once `taylored-policy.md` exists. | root policy files | `ENFORCED` | `ALERT_ON_SUCCESS` | `NO` | `taylored-policy.md` |
 | `TPR-015` | Temporal Is Local Until Unified | Do not treat repo-local temporal metadata as the universal artifact lifecycle contract until a shared lifecycle taxonomy is adopted. | repo temporal metadata | `ENFORCED` | `ALERT_ON_SUCCESS` | `YES` | `temporal-and-local-working-artifact-policy.md` |
 | `TPR-016` | No Local Workspace README Docs | Do not create `README.md`, `readme.md`, or equivalent local folder documentation files anywhere under `#LOCAL_WORKSPACE`, including nested local folders. | `#LOCAL_WORKSPACE` | `ENFORCED` | `ALERT_ON_SUCCESS` | `YES` | `file-creation-and-artifact-placement-policy.md` |
 
 Interpretation for `TPR-016`:
 
 - local-workspace lanes are operational holding surfaces, not documentation surfaces
 - canonical guidance belongs in root policy, shared process docs, owning repos, or approved external canonical systems
+
+## Registry companion
+
+The status of policy-like surfaces is governed by:
+
+- `bitpod-docs/policies/policy-registry.toml`
+
+Use the registry to distinguish active, compat, inactive, and legacy surfaces.

.agents/policy/taylored-policy.md

@@ -1,22 +1,21 @@
 <!-- GENERATED FILE. DO NOT EDIT HERE. -->
-<!-- CANONICAL SOURCE: bitpod-docs/process/taylored-policy.md -->
+<!-- CANONICAL SOURCE: bitpod-docs/policies/taylored-policy.md -->
 <!-- MIRROR ROLE: repo packet mirror -->
 # Taylored Work Policy
 
-CANONICAL SOURCE: `bitpod-docs/process/taylored-policy.md`
-LOCAL ROOT MIRROR: `$WORKSPACE/taylored-policy.md` bootstrap mirror only
-EDIT SURFACE: edit this file first; generated mirrors must not become parallel canon
+CANONICAL SOURCE: `bitpod-docs/policies/taylored-policy.md`
+EDIT SURFACE: edit this file first
 
 NAME: Taylored Work Policy
 STATUS: Active
-DATE: 2026-03-24
-VERSION: 2.0
+DATE: 2026-04-05
+VERSION: 2.1
 OWNER: Workspace / Product Development
-DESCRIPTION: Canonical repo-backed global work-policy contract for local umbrella bootstrap and cloud-visible repo distribution.
-SCOPE: Workspace-wide authority, portability, and artifact governance.
-ENTRYPOINT: repo-root `AGENTS.md` files and generated bootstrap mirrors.
-DEPENDENCIES: `AGENTS.md`, `taylored-policy-rules.md`, shared process docs.
-OVERRIDE_POLICY: Repo `AGENTS.md` may declare explicit rule exceptions listed in the registry.
+DESCRIPTION: Canonical repo-backed global work-policy contract for the BitPod-App workspace.
+SCOPE: Workspace-wide authority, portability, minimal root contract, and artifact governance.
+ENTRYPOINT: repo-root `AGENTS.md` files and root umbrella `AGENTS.md`.
+DEPENDENCIES: `AGENTS.md`, `taylored-policy-rules.md`, `policy-registry.toml`, shared process docs.
+OVERRIDE_POLICY: Repo `AGENTS.md` may declare explicit rule exceptions listed in the root policy rules.
 
 STATUS:
 
@@ -38,19 +37,23 @@ TOKENS:
 CANONICAL POLICY SURFACES:
 
 - `bitpod-docs/AGENTS.md` = canonical repo-backed policy entrypoint
-- `bitpod-docs/process/taylored-policy.md` = canonical global work-policy contract
-- `bitpod-docs/process/taylored-policy-rules.md` = canonical prohibition list
+- `bitpod-docs/policies/taylored-policy.md` = canonical global work-policy contract
+- `bitpod-docs/policies/taylored-policy-rules.md` = canonical prohibition list
+- `bitpod-docs/policies/policy-registry.toml` = canonical authority-status registry
 
-COMPATIBILITY SURFACES:
+ACTIVE ROOT SURFACES:
 
-- `$WORKSPACE/AGENTS.md` = local umbrella bootstrap mirror only
-- `$WORKSPACE/taylored-policy.md` = local umbrella bootstrap mirror only
-- `$WORKSPACE/taylored-policy-rules.md` = local umbrella bootstrap mirror only
+- `$WORKSPACE/AGENTS.md` = local umbrella router only
+- `$WORKSPACE/.codex/org-workspace.toml` = workspace metadata only
+- `$WORKSPACE/.codex/environments/environment.toml` = minimal environment metadata only
+- `$WORKSPACE/.codex/config.toml` = compatibility-only if Codex still requires an explicit instruction pointer
 
-FALLBACK FILE NAMES:
+RETIRED ROOT SURFACES:
 
-- lowercase `agents.md` may exist as a compatibility fallback only
-- lowercase files are never canonical when uppercase files exist
+- `$WORKSPACE/taylored-policy.md`
+- `$WORKSPACE/taylored-policy-rules.md`
+- `$WORKSPACE/policy.md`
+- `$WORKSPACE/.codex/policy.md`
 
 DEFAULT MODEL:
 
@@ -61,28 +64,37 @@ DEFAULT MODEL:
 
 DISCOVERY MODEL:
 
-- local umbrella bootstrap may start from `$WORKSPACE/AGENTS.md`
+- local umbrella sessions may start from `$WORKSPACE/AGENTS.md`
 - cloud and repo-local Codex runs must discover policy from files that exist inside the actual repo
-- do not rely on umbrella-root-only files for cloud-visible behavior
+- do not rely on retired umbrella-root mirror files for cloud-visible behavior
 
 READ ORDER:
 
 1. repo-root `AGENTS.md` in the active repo
-2. local packet or canonical policy files referenced by that repo-root `AGENTS.md`
+2. local repo packet or canonical policy files referenced by that repo-root `AGENTS.md`
 3. repo-specific nested `AGENTS.md` or `AGENTS.override.md`, if present
 4. task-specific canonical docs explicitly pointed to by the active instruction chain
 
+For local umbrella-root sessions:
+
+1. root `AGENTS.md`
+2. `bitpod-docs/policies/taylored-policy.md`
+3. `bitpod-docs/policies/taylored-policy-rules.md`
+4. `bitpod-docs/policies/truthfulness-and-verification-policy.md`
+5. `bitpod-docs/policies/file-creation-and-artifact-placement-policy.md`
+
 AUTHORITY MAP:
 
 - repo-root `AGENTS.md` = active runtime entry routing inside each repo
-- `bitpod-docs/process/taylored-policy.md` = global guardrails and authority model
-- `bitpod-docs/process/taylored-policy-rules.md` = prohibition IDs, enforcement state, alertability, and exception eligibility
+- `bitpod-docs/policies/taylored-policy.md` = global guardrails and authority model
+- `bitpod-docs/policies/taylored-policy-rules.md` = prohibition IDs, enforcement state, alertability, and exception eligibility
+- `bitpod-docs/policies/policy-registry.toml` = active versus compat versus legacy authority status
 - repo `AGENTS.md` = repo-specific execution instructions, workflow guidance, model defaults, and canonical doc pointers
 - repo `README.md` = orientation and navigation only
 - shared process docs = detailed semantics, naming, lifecycle, audit behavior, and packet contracts
 
 WORKFLOW POINTER:
-
+D
 - for cross-repo Linear issue-update semantics, treat `update Linear` as `make the issue materially more truthful`
 - that default preserves existing assignee/delegate by default and does not include assigning/delegating issues to Codex or mentioning `@Codex`; those actions are explicit cloud-task delegation only
 - the canonical detailed rule surface for that behavior is `$WORKSPACE/bitpod-tools/linear/docs/process/linear_operating_guide_v3.md`
@@ -112,7 +124,7 @@ KEEP IN GLOBAL POLICY CANON:
 - portability boundaries
 - root/local lifecycle guardrails
 - the structure that governs how the root policy rules are applied
-- packet and mirror discipline for cloud-visible repo distribution
+- registry and packet discipline for cloud-visible repo distribution
 
 KEEP IN REPO `AGENTS.md`:
 
@@ -168,22 +180,23 @@ SECRETS:
 
 PORTABILITY:
 
-- Taylor01 portability should rely primarily on repo-root `AGENTS.md`, `bitpod-docs/process/taylored-policy.md`, `bitpod-docs/process/taylored-policy-rules.md`, and shared canonical docs
+- Taylor01 portability should rely primarily on repo-root `AGENTS.md`, `bitpod-docs/policies/taylored-policy.md`, `bitpod-docs/policies/taylored-policy-rules.md`, and shared canonical docs
 - GitHub-native files are used only for GitHub-native behavior
 - `.github` repo may hold governance docs or automation, but it is not the sole runtime instruction source
 
-PACKET AND MIRROR RULE:
+PACKET RULE:
 
 - canonical policy is edited in `bitpod-docs`
-- distributed repo packets and local root bootstrap files are generated from canon
-- mirrored files must declare canonical source and `DO NOT EDIT HERE`
+- distributed repo packets are generated from canon
+- root runtime depends only on root `AGENTS.md`, not on root mirrored policy files
 - generated runtime packets must not become silent parallel canon
 
 ROOT REFERENCES:
 
-- `$WORKSPACE/bitpod-docs/process/taylored-policy-rules.md`
+- `$WORKSPACE/bitpod-docs/policies/taylored-policy-rules.md`
+- `$WORKSPACE/bitpod-docs/policies/policy-registry.toml`
 - `$WORKSPACE/bitpod-docs/process/read-first-protocol.md`
-- `$WORKSPACE/bitpod-docs/process/truthfulness-and-verification-policy.md`
+- `$WORKSPACE/bitpod-docs/policies/truthfulness-and-verification-policy.md`
 - `$WORKSPACE/bitpod-docs/process/codex-global-policy-packet-contract.md`
 
 TRUTHFULNESS DISCLOSURE RULE:

audit_ctl.sh

@@ -442,7 +442,10 @@ collect_queue_health() {
   working_files="$(count_files "$ROOT/local-workspace/local-working-files")"
   trash_files="$(count_files "$ROOT/local-workspace/local-trash-delete")"
   handoff_files="$(count_files "$ROOT/local-workspace/local-handoffs")"
-  pm_only_files="$(count_files "$ROOT/local-workspace/local-cj-pm-only")"
+  pm_only_files="$(count_files "$ROOT/local-workspace/local-personal-only")"
+  if [[ "$pm_only_files" -eq 0 ]]; then
+    pm_only_files="$(count_files "$ROOT/local-workspace/local-cj-pm-only")"
+  fi
   codex_state_files="$(count_files "$ROOT/local-workspace/local-codex")"
   shared_dropoff_files="$(count_files "$ROOT/local-workspace/local-shared-dropoff")"
 }

config/cleanup_zones_policy.tsv

@@ -3,10 +3,9 @@
 # - REPORT_ONLY: cleanup audit only reports metrics (counts/dup names/large files), no action pressure.
 # - STRICT_CANONICAL: canonical zone, expected to stay organized and auditable.
 
-cj_pm_dropbox|REPORT_ONLY|local-workspace/local-cj-pm-only|explicit user-managed keep zone when enabled by the selected local-workspace profile; no cleanup pressure
+local_personal_folder|REPORT_ONLY|local-workspace/local-personal-only|personal-only lane when enabled by profile; compatibility alias: local-workspace/local-cj-pm-only
 local_trash_delete|REPORT_ONLY|local-workspace/local-trash-delete|inactive disposal holding lane; do not replicate; review only for purge
 local_working_files|REPORT_ONLY|local-workspace/local-working-files|default explicit keep path for local files that are still active or under review
-local_migration_history|REPORT_ONLY|local-workspace/local-working-files/local-migration-history|temporary migration-era packet if still present; not part of canonical skeleton; keep tiny and review regularly
 legacy_agent_bootstrap|REPORT_ONLY|bitpod-docs/archive/legacy-context/sector-feeds-agent-bootstrap|archived non-feed bootstrap material moved out of sector-feeds; preserve and monitor only
 templates_registry|STRICT_CANONICAL|bitpod-tools/linear/docs/templates_registry|canonical template index and references
 learnings_ledger|STRICT_CANONICAL|bitpod-docs/archive/learnings|canonical retros/protocol learnings

linear/docs/process/durable_artifact_memory_flow_proof_v1.md

@@ -1,6 +1,6 @@
 # Durable Artifact and Memory Flow Proof v1
 
-Status: Working proof  
+Status: Retained proof (inactive by default)  
 Linked issue: [BIT-87 — Prove durable decision, memory, and artifact flow in live AI-team operations](https://linear.app/bitpod-app/issue/BIT-87/prove-durable-decision-memory-and-artifact-flow-in-live-ai-team)
 
 ## Objective
@@ -24,9 +24,9 @@ Interpretation:
 
 Decision/planning artifacts:
 
-- `/Users/cjarguello/bitpod-app/bitpod-tools/linear/docs/process/bootstrap_phase_normalization_plan_v1.md`
-- `/Users/cjarguello/bitpod-app/bitpod-tools/linear/docs/process/stage4_5_agent_stack_execution_plan_v1.md`
-- `/Users/cjarguello/bitpod-app/bitpod-tools/linear/docs/process/startup_operating_model_v1.md`
+- `$WORKSPACE/bitpod-tools/linear/docs/process/bootstrap_phase_normalization_plan_v1.md`
+- `$WORKSPACE/bitpod-tools/linear/docs/process/stage4_5_agent_stack_execution_plan_v1.md`
+- `$WORKSPACE/bitpod-tools/linear/docs/process/startup_operating_model_v1.md`
 
 Controlling issue/PR:
 
@@ -47,10 +47,10 @@ Execution lane:
 
 Representative implementation outputs:
 
-- `/Users/cjarguello/bitpod-app/sector-feeds/artifacts/runs/legacy_tuesday_track/jack_mallers_show/20260311T065208Z__status.json`
-- `/Users/cjarguello/bitpod-app/sector-feeds/artifacts/runs/legacy_tuesday_track/jack_mallers_show/20260311T065208Z__summary.md`
-- `/Users/cjarguello/bitpod-app/sector-feeds/artifacts/runs/experimental_track/jack_mallers_show/20260311T065224Z__status.json`
-- `/Users/cjarguello/bitpod-app/sector-feeds/artifacts/runs/experimental_track/jack_mallers_show/20260311T065224Z__summary.md`
+- `$WORKSPACE/sector-feeds/artifacts/runs/legacy_tuesday_track/jack_mallers_show/20260311T065208Z__status.json`
+- `$WORKSPACE/sector-feeds/artifacts/runs/legacy_tuesday_track/jack_mallers_show/20260311T065208Z__summary.md`
+- `$WORKSPACE/sector-feeds/artifacts/runs/experimental_track/jack_mallers_show/20260311T065224Z__status.json`
+- `$WORKSPACE/sector-feeds/artifacts/runs/experimental_track/jack_mallers_show/20260311T065224Z__summary.md`
 
 What this proves:
 
@@ -82,9 +82,9 @@ What this proves:
 
 Checkpoint protocol artifacts:
 
-- `/Users/cjarguello/bitpod-app/bitpod-tools/linear/docs/process/long_thread_checkpoint_protocol_v1.md`
-- `/Users/cjarguello/bitpod-app/bitpod-tools/linear/docs/process/checkpoints/thread_checkpoint_template_v1.md`
-- `/Users/cjarguello/bitpod-app/bitpod-tools/linear/docs/process/checkpoints/active_checkpoint_sector_feeds_bit77_2026-03-11.md`
+- `$WORKSPACE/bitpod-tools/linear/docs/process/long_thread_checkpoint_protocol_v1.md`
+- `$WORKSPACE/bitpod-tools/linear/docs/process/checkpoints/thread_checkpoint_template_v1.md`
+- `$WORKSPACE/bitpod-tools/linear/docs/process/checkpoints/active_checkpoint_sector_feeds_bit77_2026-03-11.md`
 
 Controlling issue/PR:
 
@@ -108,6 +108,12 @@ The current live chain is:
 
 That is a real decision -> execution -> QA/artifact -> memory/checkpoint chain.
 
+## Authority note
+
+This file is retained proof, not active execution policy. Use the policy
+registry to determine which current guide, contract, and runbook surfaces are
+still authoritative.
+
 ## What Is Still Missing
 
 This proof should not be overstated.

linear/docs/process/global_artifact_naming_policy_v1.md

@@ -4,6 +4,6 @@ Compatibility pointer.
 
 Primary shared policy now lives at:
 
-- `/Users/cjarguello/BitPod-App/bitpod-docs/process/global-artifact-naming-policy-v1.md`
+- `/Users/cjarguello/BitPod-App/bitpod-docs/policies/global-artifact-naming-policy-v1.md`
 
 Use that file for current naming rules.

linear/docs/process/isolation_mode_retirement_and_hardening_mapping_v1.md

@@ -1,6 +1,6 @@
 # Isolation Mode Retirement and Hardening Mapping v1
 
-Status: Working baseline  
+Status: Retained baseline (inactive by default)  
 Primary issue: [BIT-74 — Execute post-bootstrap local scope hardening window after migration closeout](https://linear.app/bitpod-app/issue/BIT-74/execute-post-bootstrap-local-scope-hardening-window-after-migration)
 
 ## Objective
@@ -14,8 +14,8 @@ Make the current truth explicit:
 
 Policy artifacts still exist:
 
-- `/Users/cjarguello/bitpod-app/local-workspace/local-codex/policy/isolation/enforcement_state.json`
-- `/Users/cjarguello/bitpod-app/local-workspace/local-codex/policy/isolation/violation_queue.json`
+- `$WORKSPACE/local-workspace/local-codex/policy/isolation/enforcement_state.json`
+- `$WORKSPACE/local-workspace/local-codex/policy/isolation/violation_queue.json`
 
 Current state is dormant:
 
@@ -25,9 +25,9 @@ Current state is dormant:
 
 Last known implementation exists only in quarantined legacy paths:
 
-- `/Users/cjarguello/bitpod-app/local-workspace/local-trash-delete/bitpod/scripts/isolation_ctl.py`
-- `/Users/cjarguello/bitpod-app/local-workspace/local-trash-delete/bitpod/tools/isolation/cli.py`
-- `/Users/cjarguello/bitpod-app/local-workspace/local-trash-delete/bitpod/tools/isolation/runtime.py`
+- `$WORKSPACE/local-workspace/local-trash-delete/bitpod/scripts/isolation_ctl.py`
+- `$WORKSPACE/local-workspace/local-trash-delete/bitpod/tools/isolation/cli.py`
+- `$WORKSPACE/local-workspace/local-trash-delete/bitpod/tools/isolation/runtime.py`
 
 ## Retirement decision
 
@@ -87,6 +87,12 @@ If OpenClaw or another operator surface later needs stronger isolation:
 - implement it in an approved active path
 - verify it in the current runtime/host model
 
+## Authority note
+
+This file is retained as an explanatory mapping, not as an active operating
+policy. Current authority lives in the active policy registry and the approved
+hardening/runtime boundary docs.
+
 ## Allowed remaining legacy state
 
 The dormant policy files and skill may remain temporarily as historical inspection aids.

linear/docs/process/vera_qa_lane_contract_v1.md

@@ -80,14 +80,16 @@ If the handoff packet is incomplete, QA should reject the handoff and ask Taylor
 
 Every dedicated QA execution must produce a `verification_report.md`-style artifact with:
 
-1. verdict: `PASSED` or `FAILED`
+1. verdict: `PASSED`, `FAILED`, or `SKIPPED`
 2. environment matrix
 3. critical acceptance criteria with evidence per criterion
 4. `this failed QA because ...` section when verdict is `FAILED`
-5. optional low-risk fix hints only when obvious
-6. final line:
+5. `this QA was skipped because ...` section when verdict is `SKIPPED`
+6. optional low-risk fix hints only when obvious
+7. final line:
    - `QA_VERDICT: PASSED`, or
-   - `QA_VERDICT: FAILED`
+   - `QA_VERDICT: FAILED`, or
+   - `QA_VERDICT: SKIPPED`
 
 Allowed storage targets: