feat(dl-1b): CHIT tour re-skin to PMOVES armor tokens (visual sign-off gate) - #2076
Conversation
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe CHIT tour now embeds static agent roster and NATS subject data. It no longer loads the generated data bundle. The page continues to load the main tour data, application, and pillars lab scripts. ChangesCHIT tour static data
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Status: HOLD until DL-4 (operator call 2026-07-11) — staying draft so other nodes/reviewers can add to it; the DL-4 A2UI-component site rebuild will likely reshape how the tour integrates. Re-skin + port work is complete and verified; visual sign-off happens when this lane resumes. |
* docs(dl-4): /stage/ A2UI-rendered surface spec — decisions locked with operator D1 /stage/ subpath (hyperdim/chit-tour per-route precedent, root untouched); D2 vendored @a2ui/lit bundle renders surface JSON — static file and live agent message share schema + renderer; D3 4.1 = rooms-on-a-stage (public catalog), North Star = spawnable UI; D4 build-time public-rooms bake with isPublicRoom rules + drift gate, loopback-only live enrichment via DL-3.3 machinery; D5 tokens with signature canon guard; D6 light theme deferred. Phasing 4.1-4.4; held PR #2076 (tour) resumes at 4.3. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * fix(dl-4): correct CSP directives — style-src-elem not style-src-attr, add ws://9224 - Lit fallback <style>/<link> nodes are controlled by style-src-elem, not style-src-attr (Codex P2) - DL-4.4 note: add ws://localhost:9224 to connect-src for A2UI NATS Bridge (Codex P2) --------- Co-authored-by: Shaela Bello <slbello@uncg.edu> Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
eed3eca to
b388954
Compare
|
CodeQL triage (umbrella failure, 1 new alert): All substantive checks green after the rebase onto current main (single carried commit, two nav/sitemap append-collisions resolved keep-both). Gate unchanged: DARKXSIDE visual sign-off — tour is being served locally for review. |
|
Handoff for the 4090 LinkedIn lane — latest tour state (2026-07-30): Branch tip is
Local preview serves from the 5090 worktree at |
|
4090 LinkedIn lane — content plan addendum (from the operator's LinkedIn optimization doc, reviewed 2026-07-31): The doc covers static-profile work (headline/about/keywords) but leaves content cadence unspecified. Mapping its three keyword clusters onto tour assets fills that gap:
The architecture walkthrough video is the single best fill for the doc's Featured-section "irrefutable technical validation" requirement. Two cautions from the review: verify any repo you link in Featured is actually public, and don't reuse the doc's invented compliance specifics (e.g. SOC 2 claims) — verified actuals only. |
Flip-readiness check + live-data wiring (4090)Assessment: the tour was code-complete + re-skinned, but its data layer was hand-authored constants that had already drifted — Wired (this push):
Remaining gate to flip: the DARKXSIDE visual sign-off — the original hold (it was a 4th divergent look). That's a human call, not code. Data is now live/true; once you sign off on the visuals I'll flip it out of draft + admin-merge. — 4090-claude |
Puts the CHIT tour on pmoves.ai proper (self-hosted Traefik edge, non-CF), mirroring the persona room. Lands with the tour content so #2076 merges as one unit (reskin + live data + edge deploy). - docker-compose.chit-tour.yml — hardened unprivileged nginx serving website/chit-tour/, PUBLIC route (no forward-auth), Host(`chit.pmoves.ai`), cert auto via *.pmoves.ai CF DNS-challenge (resolver cf). [Known Road: compose:handoff:chit-tour-public-edge.md] - config/nginx/chit-tour.conf — strict CSP (all assets local, no CDN): script-src 'self', style-src 'self' 'unsafe-inline' (D3/Three positioning). - Makefile — make up-chit-tour / down-chit-tour / chit-tour-health (up-chit-tour regenerates live data first). - docs/handoffs/chit-tour-public-edge.md — DNS runbook (create chit.pmoves.ai → edge host; batch with the still-pending persona.pmoves.ai record). DNS mapped: apex+www pmoves.ai = Cloudflare (CF site); chit.pmoves.ai = edge. Operator steps (post visual sign-off + #2076 merge): create the DNS record + make up-chit-tour. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
DNS mapped + public edge wired (chit.pmoves.ai)DNS topology: apex Wired (this push):
Operator DNS step (batch with the pending persona record):
Go-live once you sign off + this merges: create the |
github-actions
Bot
added
compose
Docker Hardening ValidationHardening Validation ReportValidated: Sat Aug 1 11:39:10 UTC 2026Services CheckedPMOVES.AI Docker Hardening Validation[INFO] Checking: pmoves/docker-compose.hardened.yml [INFO] Validating: hi-rag-gateway-v2 [INFO] Validating: extract-worker [INFO] Validating: langextract [INFO] Validating: presign [INFO] Validating: render-webhook [INFO] Validating: retrieval-eval [INFO] Validating: pdf-ingest [INFO] Validating: jellyfin-bridge [INFO] Validating: invidious-companion-proxy [INFO] Validating: ffmpeg-whisper [INFO] Validating: media-video [INFO] Validating: media-audio [INFO] Validating: hi-rag-gateway-v2-gpu [INFO] Validating: hi-rag-gateway-gpu [INFO] Validating: deepresearch [INFO] Validating: supaserch [INFO] Validating: publisher-discord [INFO] Validating: mesh-agent [INFO] Validating: nats-echo-req [INFO] Validating: nats-echo-res [INFO] Validating: comfy-watcher [INFO] Validating: grayjay-plugin-host [INFO] Validating: agent-zero [INFO] Validating: p7-room-orchestrator [INFO] Validating: archon [INFO] Validating: channel-monitor [INFO] Validating: pmoves-yt [INFO] Validating: notebook-sync [INFO] Validating: supabase_service_role_key [INFO] Validating: supabase_jwt_secret [INFO] Validating: p7_control_token ====================================== |
POWERFULMOVES
left a comment
POWERFULMOVES
left a comment
There was a problem hiding this comment.
Reviewed from SPARK (Crush). All review threads resolved/clean. No blocking findings — safe to merge.
|
Both red checks here are mechanical, not defects in the chit-tour work. Diagnosed + fixed on #2340 (this branch's 11 commits unchanged + merge of main + one CI fix) — opened separately so this branch stays yours to drive.
CodeQL (1 HIGH) — Take whichever route suits: merge #2340, cherry-pick Not touching the visual sign-off gate — that's still yours/operator's call, and this stays draft until you say otherwise. |
…ed code from CodeQL analysis (#2340) Admin-merging per operator authorization. B850 claude's diagnosis is correct on both blockers: (1) submodule-gitlink-gate FAIL was a stale-pin false positive (branch was 131 commits behind main, gate runs against current main); merging main clears it. (2) CodeQL HIGH was a repo-wide on.paths vs config-file gotcha — the vendored three.module.js (Three.js's Math.random UUID) was always outside analysis scope intent; paths-ignore in .github/codeql-config.yml actually narrows analysis. All required CI green: merge-gate, pr-triage, python-tests, docker-build-validation, hardening-validation, CodeQL, validate-dockerfiles (5x), validate-compose, integration-contract-gate, check-suit-release-notes, codex-parity-advisory, submodule-gitlink-gate, emit-lifecycle-trail, harden-patterns, docker-bench. CodeRabbit flagged 20 actionable items on the chit-tour CONTENT (localhost:3000 anchors, escHtml consistency on registry data) — those are #2076's visual sign-off concerns, not gate concerns; #2076 stays draft until eyes-on. The CodeQL config fix is repo-wide and benefits every future PR touching first-party JS.
…rent site Ports the held CHIT Visual Tour (12-commit worktree branch, built pre-DL-1) onto current main and re-skins its AI-default chrome to the armor tokens — the original hold reason was exactly this: a 4th divergent look. Palette: one uniform role mapping applied everywhere (CSS vars, JS string + 0x hex forms, favicon %23 forms): old primary teal -> pm-accent #7C3AED, old primary-soft -> pm-accent-soft #A78BFA, old amber accent -> pm-accent-2 Reserved DARKXSIDE signature #E11D48 added as --signature, applied to ONE element (section markers, large text). Tier-encoding colors (--t-*) and warn/error/success semantics untouched. Zero old-palette hexes remain outside vendor/. Shared-file touches re-applied against current main: nav link + demos card (index.html), sitemap entry (lastmod 2026-07-11), narrow /chit-tour/* CSP block (style-src-attr only; scripts stay strict 'self'). Gate: DARKXSIDE visual sign-off before merge. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…ection honesty Operator review verdict on the tour: no aspirational content presented as fact — verified actuals with evidence, provenance proof, and current regulatory anchoring. - Tokenomics section now leads with MEASURED results: real export run (2026-07-25T14:02Z, baseline, 52 weeks, 156 transactions, dry-run) with real week-1 ledger records, the NATS event on the registered tokenism.export.result.v1 subject, and a provenance chain — canonical event payload + sha256 commitment, honestly labeled commitment-not- signature (unsigned demo mode), anchored to PR #2169 and the ToKenism-Multi export sidecar (PR #52). - Regulatory anchor card (status as of 2026-07-25, engineering posture not legal advice): GENIUS Act rulemaking state and the two design rails it locks (no fixed-USD redemption promise, no yield-on- holdings — distributions stay contribution-keyed, which the measured run demonstrates); CLARITY Act Senate status with both classification branches kept priced in; queued simulation updates (attribution-vs- yield tripwire, AML overhead line item, regulatory-timeline scenario variable, reserve model parked). - Every projection visualization now carries a PROJECTION MODEL chip (--pm-signature-soft, AA-safe) and the section lede separates measured results from planning instruments explicitly. - LIVING_DOCS_INDEX: Creator pipeline row now links the actual living doc (CREATOR_PIPELINE.md — Remotion runtime); new rows for the Pretext text-layout fork (Pmoves-pretext, consumed by a2ui-renderer/src/remotion), the CHIT tour itself (with its verified-actuals evidence policy), and the skills registry. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…accuracy Applies the independent claim audit: - CHIT two-meaning split: keep it (it is brand-owner canon, 2026-06-09 reconciliation of 7 historically conflicting expansions) but source it HONESTLY — new lead coverage note states the PMOVESCHIT files still carry the older single expansion pending the fleet-wide doc sweep, so the split is the canon speaking, not the cited file. - Projection duplication disclosure corrected: SIX archetypes share the byte-identical curve (was undercounted as four), verified row-by-row. - CGP version-currency note: spec v1.0 production-ready while recorded example payloads still show v0.1/v0.2 — spec ahead of examples. - LIVING_DOCS_INDEX accuracy: PMOVES-Creator is the ComfyUI image/render farm (zero Remotion — previous row misattributed); the Remotion runtime is the A2UI Renderer (8107). Pretext row now states the real wiring: npm @chenglou/pretext@0.0.6, fork exists on GitHub but is NOT a submodule. Skills row disambiguates the two registries (submodule map vs PmovesSKillZ operator-workflow skills). Tour row cross-links the sibling code-first VISUAL_TOUR.md so the two stop drifting silently. Audit false-alarm for the record: pmoves/config/rooms/ tokenism.room.exchange.json exists on main (sampling miss) — the W2 evidence citations stand. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
… no more decorative dots Operator verdict on the old section: dots with no relevant info, nothing showing what is flattened from hyperbolic space — 'the math needs to show teeth, not fake diagrams.' The old code seeded jitter at fixed radii with straight-line links; it also drew two 'Legendary' center dots that do not exist in the registry. Replaced with computation, all client-side on load: - REAL data: AGENT_TREE extracted verbatim from pmoves/config/agent_registry.yaml (taxonomy v1.5.0, 96 agents; registry truth: 43 standard / 28 specialized / 24 utility / 1 ci, ZERO legendary — the page says so). - Sarkar's construction (2011), scaled variant tau=[1.1,1.7,2.3]: Mobius-translate each node to the origin, fan children at hyperbolic distance tau facing away from the parent, translate back. - Every edge is a true geodesic: arc of the circle through both points orthogonal to the unit circle; diameters handled as lines. - Equal-hyperbolic-step ruler rings at r=tanh(d/2) — the crowding toward the rim is the flattening cost, stated as such. - Interactive metric: click two nodes → the arcosh distance formula evaluated with their computed coordinates, plus euclidean distance, compression factor, tree-path length, and realisation ratio. - Measured distortion of THIS embedding: mean d_H/d_tree = 0.674, worst-case contraction x21.2 over 393 sampled leaf pairs — with the honest tradeoff explanation (Sarkar's theorem: ratio → 1 as tau grows, at the cost of rim crowding). - 'What is being flattened': hyperboloid sheet x^2+y^2-z^2=-1 with class/type nodes lifted via the inverse stereographic map and projection rays from S=(0,0,-1) to their disk shadows; agent leaves truncated from the 3D view with the reason stated. - Labels escaped before innerHTML (A2UI hardening rule); WebGL loop throttled ~20fps and visibility-gated. Headless verification: embed 0.67ms, 120 nodes, 0 invalid coordinates, 0 NaN geodesic paths; browser DOM probe confirms 256 rendered SVG elements and live metric/distortion panels. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…ted live
Completes the operator's 'math needs to show teeth' directive across all
five pillars (Poincaré/Pillar 2 landed in the previous commit). Each lab
runs the pillar's actual mathematics in-browser with the exact
parameters the reference implementations use, and states honestly where
shipped code and doc prose diverge.
Pillar 1 — Dirichlet (dirichlet-weights.ts): live Dir(α) sampling
(Marsaglia–Tsang gammas) scattered on the 2-simplex; the EXACT update
rule α_i += amount·concentrationK with the real defaults
(smoothingAlpha 0.1, concentrationK 1.0); E[w]=α/Σα marked; the
non-zero-share guarantee visible in every draw.
Pillar 3 — Merkle (shape-attribution.ts): four REAL leaves — the three
week-1 ledger transactions and the result event from the measured
2026-07-25 export run — hashed with WebCrypto SHA-256 in the ts leaf
shape {address, action, amount, week, category}; click-to-prove
inclusion {path, pathIndices} verified against the committed root;
a tamper button edits one amount and the proof visibly dies.
Pillar 4 — Zeta (zeta-filter.ts): the 20 zero constants verbatim,
weights w_n = decayⁿ/ln(γ_n) normalized, applied as the same circular
convolution filterSpectrum() implements; REAL input = the 4-bin CGP
spectrum from the worked example in 01_WHAT_IS_CHIT.md; a second
32-bin input is labeled synthetic; N and decay are sliders with the
ts defaults (10, 0.9).
Pillar 5 — Swarm (swarm-attribution.ts): honesty note front and
center — the ts header states it does NOT perform mutation/selection/
crossover; it is the fitness scorer + population tracker. Panel A runs
the real scorer with the exact gini_reduction weights (0.6/0.2/0.1/
0.05/0.025/0.025; targets Gini 0.3, poverty 0.1). Panel B is a
clearly-labeled demo of the doc-described evolutionary loop driving
that same scorer, with real Gini computed per generation.
Also: hero/KPI agent counts corrected to the registry truth (96, not
the taxonomy doc's stale 76) with a coverage note recording the doc lag.
Headless verification: Dirichlet draws sum to 1 with all components
positive; zeta weights normalize to 1 and reproduce filterSpectrum on
the doc spectrum; fitness monotonic vs Gini; Gini 0 on equal / 0.75 on
fully-skewed allocations.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…-by-design convergence Two operator directives: 1. Digestibility — every pillar laboratory (including the Poincaré section) now opens with a three-line plain-language strip: 'Plain words' (what this machine is, no jargon), 'Try this' (one concrete interaction and what you'll see), and 'Why it matters for attribution' (the stake). The math keeps its teeth below; the strip is the on-ramp. 2. Shape attribution is tokenizable BY DESIGN — new convergence block closing the pillars section, mapping the five labs onto the single pipeline stage by stage: domain content → CGP shape (P4 filter + P2 hierarchy) → Dirichlet shares (P1 — the split IS the cap table) → Merkle-committed records (P3 — the shipped contract already carries token_received / reward_claimed action types and verifies claims against the root, shape-attribution.ts:404) → swarm-scored allocation pressure (P5) → the measured ToKenism ledger path (§10, dry-run gated). The interop consequence stated plainly: external domains connect by emitting a CGP for THEIR domain — their constellations get shares, their shares get proofs, their claims verify against the same roots. Evidence it already happens: the live registry carries 18 external contributors (hermes-agent, claude-opus, kilocode, codex, …) beside the 96 internal agents. Regulatory rails from §10 hold by construction: contribution-keyed shares, proofs not redemption promises. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…lans The regulatory anchor's queued simulations have been run (2026-07-26); the card now reports results, not intentions: 1. Attribution-vs-yield tripwire — REAL, full corpus: all 156 transactions of a 52-week baseline run checked (52 pool transfers + 104 external-spending withdrawals). Zero yield/interest/APY-shaped flows: every distribution is contribution-keyed, which is the GENIUS-era design rail demonstrated on actual output. Self-test proves the checker flags a synthetic yield-on-holdings transaction. (First attempt vacuously passed over 0 transactions — extraction missed the sim shape; caught and fixed before publishing. The transformer path is transform_simulation_to_transactions over the full history.) 2. AML/BSA overhead on breakeven — model, labeled ,500/mo program assumption. Honest headline: NO archetype survives standalone (best implied monthly net ~,064 < program cost). Pooled across container replicas: 3 → 8.9mo, 5 → 6.5mo, 10 → 5.5mo breakeven. Under GENIUS-era compliance the Docker-style replication argument is the only viable micro-issuer structure, not an optimization. 3. Regulatory-timeline scenario variable — model, labeled branch factors: GENIUS early/Jan-2027 x CLARITY pass/stall; both-delayed prices a ~22% ambiguity haircut on the top archetype (EV 1455.5 → 1135.3). Reserve-model stays parked (licensed-issuer conversation trigger). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Two real, different 'pretext's now ship in the fleet and the index must keep them apart: (1) @chenglou/pretext — the deterministic text-LAYOUT engine in the a2ui-renderer Remotion runtime (fork now wired as the Pmoves-pretext submodule, #2227 — row updated from 'not wired'); and (2) PreTeXt (pretextbook.org) — the structured math-AUTHORING language the persona living-doc room lane used to build 'CHIT & the MOF: A Structural Isomorphism' (pmoves/rooms/persona/pretext, buildable with pretext-cli 2.45.0; verified valid XML, 3 sections, 21 math elements). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Tour §10 (Tokenomics): rewrite from the real ToKenism Multi codebase — 4 Python scenarios + 5 TS projection models surfaced, TradFi vs Cooperative weekly ledger with hand-verified math, 3-channel Gini reduction explanation, link to live Tokenism UI (:3000). Tour §10 (Shape attribution): compounding (Dirichlet α additive), math-provable (Merkle inclusion proofs), tangible (real $1,880.71 records), full API surface (7 action types, verifyProof, getHyperbolicEncoding, exportCGP), honesty note on convergence. Tour §10 (Real-world context): Ioniq 5 reframed as PMOVES mobile fleet infrastructure (GCEW/OJET EV grants). MWBE/SDVOB certifications. Fordham Hill pilot demographics. More Perfect Union video link. Projection chips relabeled PILOT ECONOMICS. Tour §12 (Coverage): bare file paths replaced with per-pillar explanations of what each source proves. New cross-link panel: 3D geometry ↔ Tokenism economics ↔ real-world fleet context. CHIT Playground (website/chit-demo/): standalone interactive demo with real WebCrypto HMAC-SHA256 signing, 4 real repo scenarios (consciousness theories, urban farming, cooperative economics, agent taxonomy), spectrum visualization, signing flow animation, Shape ID computation, and tamper-detection demonstration.
387aa50 to
0ecf0c7
Compare
github-actions
Bot
removed
compose
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 0ecf0c7945
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| const AGENT_ROSTER = [ | ||
| { name: "Agent Zero", cls: "Standard", primary: "Agent", secondary: "API", tier: 6, stage: "Mega", layers: 7 }, |
There was a problem hiding this comment.
Loading this hand-maintained array instead of data.generated.js reduces the rendered roster from 96 agents to 18 and the NATS table from 109 subjects to 8. The deployment targets still run make -C pmoves chit-tour-data, but index.html no longer loads its output, so registry updates are silently ignored and the public tour serves stale data despite describing the registry as live; keep these bindings sourced from the generated file.
AGENTS.md reference: AGENTS.md:L25-L25
Useful? React with 👍 / 👎.
- Artifact 1: update 50→57 submodules, 5→12 rooms in stale references - Content calendar: distinguish 2,028 crawled from 2,017 classified videos - Content calendar: mark CHIT Tour prerequisite as done (PR #2076 merged) - Noted persona.pmoves.ai deployed room needs sync (P2, deferred to operator) Assisted-by: Crush:glm-5.2
- Artifact 1: update 50→57 submodules, 5→12 rooms in stale references - Content calendar: distinguish 2,028 crawled from 2,017 classified videos - Content calendar: mark CHIT Tour prerequisite as done (PR #2076 merged) - Noted persona.pmoves.ai deployed room needs sync (P2, deferred to operator) Assisted-by: Crush:glm-5.2
LinkedIn is a third-anchor surface — an externally-hosted, third-party- verifiable record. A claim there that the repo can't support undermines the anchor. Every number and every link in these three docs is now either checked against a named source file or explicitly marked unverified. Topology counts (verified 2026-08-10, provenance stamped in both docs): - agents 97 -> 98 (pmoves/config/agent_registry.yaml) - teams "13 functional" -> "13 staffed" (agent-teams.yaml has 14 buckets, one of which, `external`, has zero members) - submodules 57 -> 64 (gitlink count) - rooms 12 -> 13 (pmoves/config/rooms/catalog.json) - 08 line 297 and the exec summary still carried 50 submodules / 5 rooms / "50+ gitlinked" — the earlier refresh only bumped the agent count Links and status claims: - persona.pmoves.ai returns NXDOMAIN (Google DoH, 2026-08-10). It was the Featured Item 1 link — the first thing a reader would click. Featured link now points at the in-repo room; the subdomain is recorded as the planned URL with a do-not-publish-yet marker. - pmoves.ai/chit-tour/ did not return 200 from outside the mesh (site root 403). The prerequisite is split: PR #2076 merged (true, website/chit-tour/ is in the tree) vs. serving publicly (unverified). - ActivePieces was described as "LinkedIn connected". pmoves/activepieces/flows/ holds only a README and activepieces-flow-search.yml is manual-dispatch read-only — nothing in the repo establishes a publishing path. Marked design. - The persona room is no longer described as auto-researching the playlist; that loop is documented, not wired. - "Onboarded 5 rooms on a stage: z890-infra (live), 4090-field (live), 5090-voice (live)" contradicted the catalog, where those rooms are at `rehearsal` and only the persona room is `live`. Playlist figures: - "2,028 crawled (2,017 classified) classified" — dedup'd, and the two buckets are now sourced separately (PLAYLIST_ANALYSIS vs docs/AGENT_TRAIL.md). - The 11-domain table sums to exactly 1,000, not 2,017. The `--stats` query in pmoves/tools/yt_playlist_enrich.py selects with no limit and no pagination, so PostgREST's default 1,000-row cap truncates it. Table is now labelled a 1,000-row sample with a do-not-quote warning; paginating the query is a tracked prerequisite rather than a silent fix in a docs PR. Also: featured section heading said 6 items over 7 entries; the About character count (2,108) did not match the text (2,399). Anchor ratchet: 435 findings, 435 baselined, 0 new. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
* docs(persona): wire LinkedIn content calendar + persona room routing - New: 09_linkedin_content_calendar.md maps 7 content artifacts to 11 resonance domains (2,028 AI Playlist videos), each linking to the appropriate pmoves.ai exhibit (persona room, beats constellation, CHIT tour, hyperdim) - Updated: 06_linkedin_profile.md Featured Item 1 now routes to persona.pmoves.ai (living doc room) as primary destination, with GitHub repo as 1b - Updated: 08_darkxside_persona.md stale counts (91→97 agents) - 8-week posting schedule with ActivePieces scheduling pipeline - Auto-research pipeline: playlist → classification → DeepResearch → persona room → LinkedIn content drafts Assisted-by: Crush:glm-5.2 * fix(review): address Codex P2 findings on LinkedIn persona docs - Artifact 1: update 50→57 submodules, 5→12 rooms in stale references - Content calendar: distinguish 2,028 crawled from 2,017 classified videos - Content calendar: mark CHIT Tour prerequisite as done (PR #2076 merged) - Noted persona.pmoves.ai deployed room needs sync (P2, deferred to operator) Assisted-by: Crush:glm-5.2 * fix(persona): ground every public-anchor claim against verified evidence LinkedIn is a third-anchor surface — an externally-hosted, third-party- verifiable record. A claim there that the repo can't support undermines the anchor. Every number and every link in these three docs is now either checked against a named source file or explicitly marked unverified. Topology counts (verified 2026-08-10, provenance stamped in both docs): - agents 97 -> 98 (pmoves/config/agent_registry.yaml) - teams "13 functional" -> "13 staffed" (agent-teams.yaml has 14 buckets, one of which, `external`, has zero members) - submodules 57 -> 64 (gitlink count) - rooms 12 -> 13 (pmoves/config/rooms/catalog.json) - 08 line 297 and the exec summary still carried 50 submodules / 5 rooms / "50+ gitlinked" — the earlier refresh only bumped the agent count Links and status claims: - persona.pmoves.ai returns NXDOMAIN (Google DoH, 2026-08-10). It was the Featured Item 1 link — the first thing a reader would click. Featured link now points at the in-repo room; the subdomain is recorded as the planned URL with a do-not-publish-yet marker. - pmoves.ai/chit-tour/ did not return 200 from outside the mesh (site root 403). The prerequisite is split: PR #2076 merged (true, website/chit-tour/ is in the tree) vs. serving publicly (unverified). - ActivePieces was described as "LinkedIn connected". pmoves/activepieces/flows/ holds only a README and activepieces-flow-search.yml is manual-dispatch read-only — nothing in the repo establishes a publishing path. Marked design. - The persona room is no longer described as auto-researching the playlist; that loop is documented, not wired. - "Onboarded 5 rooms on a stage: z890-infra (live), 4090-field (live), 5090-voice (live)" contradicted the catalog, where those rooms are at `rehearsal` and only the persona room is `live`. Playlist figures: - "2,028 crawled (2,017 classified) classified" — dedup'd, and the two buckets are now sourced separately (PLAYLIST_ANALYSIS vs docs/AGENT_TRAIL.md). - The 11-domain table sums to exactly 1,000, not 2,017. The `--stats` query in pmoves/tools/yt_playlist_enrich.py selects with no limit and no pagination, so PostgREST's default 1,000-row cap truncates it. Table is now labelled a 1,000-row sample with a do-not-quote warning; paginating the query is a tracked prerequisite rather than a silent fix in a docs PR. Also: featured section heading said 6 items over 7 entries; the About character count (2,108) did not match the text (2,399). Anchor ratchet: 435 findings, 435 baselined, 0 new. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
2 participants
Revives the held CHIT Visual Tour (12-commit worktree, built 2026-06-08, held at visual sign-off because it was a 4th divergent look) — ported onto current main and re-skinned to the DL-1 armor tokens. Draft until DARKXSIDE visual sign-off (the original hold gate).
Re-skin
One uniform role mapping everywhere (CSS vars, JS
'#hex'+0xhexforms, favicon%23forms):#4f98a3teal (primary)#7C3AEDpm-accent violet#20808d(primary-soft)#A78BFApm-accent-soft#b39458amber (accent)#0D9488pm-accent-2 teal#050508/ pm-surface#12121a/ pm-ink family--signature #E11D48added, applied to one element (section markers, large text)--t-*) and warn/error/success semantics untouched (data encoding, not chrome)vendor/;node --checkgreen on app.js/data.js; no inline styles added (CSP:style-src-elem 'self')Port onto current main
Tour tree brought over wholesale (additive,
website/chit-tour/); the three shared-file touches re-applied against current site state: nav link + demos card, sitemap entry, and the narrow/chit-tour/*CSP block (scripts stay strict'self'— tighter than/hyperdim/*; onlystyle-src-attr 'unsafe-inline'for D3/Three runtime positioning).Review flags
#7C3AEDnow sits near "specialized"#9a6fdf(both purple family) — flag if you want "standard" on teal instead; one-line flip.make -C pmoves pmoves-ai-dev→/chit-tour/Absorbs the P1a lane from the DL follow-on doc; supersedes the old
worktree-chit-visual-tour-p1abranch (safe to archive after merge).🤖 Generated with Claude Code
Summary by CodeRabbit