docs(persona): LinkedIn dual-positioning + automation fabric + living-doc room plan - #2234
Conversation
…-doc room plan 06_linkedin_profile.md — reframed founder-only → DUAL (founder + Applied AI Architect), per notes2.md: - Headline: new primary (Applied AI Architect + founder + open-to-roles); founder headline kept as alt. - About: rewritten to lead with an availability statement + plain-language 'what I do', PMOVES specifics as support (2,108/2,600). - New §7 PMOVES→employer-language translation table + lead line. - Automation fabric represented: 34 n8n flows + ActivePieces (Experience bullets, Featured Item 6, Skills cluster, SEO keywords). - Filled pending Featured links to real repo docs (AGNOTE4482, Grand Convergence); investor/financial link left as an explicit operator TODO (keep private). 07_linkedin_living_doc_room.md (NEW) — design plan for the profile as a living-doc 'room' on pmoves.ai proper (non-CF): Remotion walkthrough (a2ui renderer) + PreTeXt technical panels + website/rooms design tokens, hosted behind the #2221 Traefik edge. Scope-only; open decisions (host, PreTeXt vs MyST/Quarto, public-vs-gated) listed for sign-off before any build. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
Warning Review limit reached
Next review available in: 50 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 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 |
![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: 3b4cfd5460
ℹ️ 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".
|
|
||
| ### Featured Item 6: Automation Fabric — 34 n8n Flows + ActivePieces | ||
| **Link:** `https://github.com/POWERFULMOVES/PMOVES.AI/tree/main/pmoves/n8n/flows` | ||
| **Description:** 34 production n8n workflows wiring PMOVES services to each other, to the CHIT geometry bus, and to external SaaS — finance sync (Firefly-III → Supabase → CGP), health tracking (wger → weekly CGP), media pipelines (audio/video analysis, ComfyUI generation, social publishing, content-approval gates), voice agents (Discord/Telegram, platform router, vibevoice/qwen/wan → CGP), CI/infra (GitHub runner autoscaler, webhook processor), and research/ingestion (DeepResearch, LangExtract, YouTube docs diff). Paired with an ActivePieces low-code workspace for cross-SaaS orchestration. Automation as first-class infrastructure — not glue, but connective tissue. |
There was a problem hiding this comment.
Before this copy is published on LinkedIn, avoid calling all 34 workflows “production”: every JSON definition at the linked pmoves/n8n/flows mirror currently has active: false, several are explicitly named stub/demo/debug, and pmoves/docs/automation/AUTOMATION_LANDSCAPE_2026-07-22.md says runtime activation still needs verification. The same audit describes Activepieces as operator-external with zero repository footprint, so the linked evidence cannot substantiate that half of the featured item either; describe these as tracked workflow definitions and clarify their verified deployment status, or add runtime evidence.
Useful? React with 👍 / 👎.
| | **Content model** | The profile as structured data (headline, about, experience, skills, featured, translation) | `06_linkedin_profile.md` → parsed/front-mattered | | ||
| | **Room shell** | Page/layout using website design tokens (fonts, `hyperdim` viz, `embeds`) + rooms-on-a-stage framing | `website/` (`assets`, `fonts`, `hyperdim`, `embeds`), rooms catalog | | ||
| | **Remotion layer** | 3-min architecture walkthrough + short loops (beats→code, convergence wave, "agents read the room") | a2ui Remotion renderer (headless render → MP4/frames → served assets) | | ||
| | **PreTeXt layer** | Deep technical docs (CHIT math, MOF isomorphism, CGP {δ,Hz,κ,A,F}) authored once, rendered to accessible HTML+math | PreTeXt (XML → HTML/MathJax); source from `architecture/` docs | |
There was a problem hiding this comment.
If this room is intended to demonstrate the existing PMOVES Remotion/Pretext skill, this substitutes an unrelated publishing system: the A2UI renderer depends on @chenglou/pretext, and pretextLayout.ts uses it for deterministic canvas text layout, whereas this row specifies the academic PreTeXt XML-to-HTML/MathJax tool, which is not the renderer or fork already integrated here. Following the plan would therefore add a different dependency and fail to demonstrate the repository's current living-doc capability; either design the panels around the existing Pretext layout engine or explicitly scope academic PreTeXt as a separate new integration.
Useful? React with 👍 / 👎.
| ## 6. Phases | ||
|
|
||
| 1. **Content model** — front-matter/parse `06_linkedin_profile.md` into structured data; single source of truth (LinkedIn paste + room both derive from it). | ||
| 2. **Room shell** — static page with website/rooms design tokens; sections mirror the profile; register the catalog entry (rehearsal stage). |
There was a problem hiding this comment.
Registering only a catalog entry in this phase leaves the proposed room unusable: both loadRooms() and P7's CatalogLoader.get_manifest() immediately resolve the entry's manifest filename and fail when the per-room JSON is absent or schema-invalid. Add creation and validation of a matching pmoves/config/rooms/<room>.json manifest to this phase before catalog registration; the room topology contract requires both artifacts.
AGENTS.md reference: AGENTS.md:L7-L7
Useful? React with 👍 / 👎.
1 participant
Reworks the LinkedIn persona profile per your direction + notes2.md, and scopes the living-doc room.
06_linkedin_profile.md — dual positioning (founder + Applied AI Architect)
Founder, PMOVES.AI | Principal Applied AI Architect | Agentic Systems, RAG, AI Deployment & Local-First Infrastructure | Hiring + Open to Mission-Aligned Roles; founder headline kept as an alt.07_linkedin_living_doc_room.md (new) — design plan
The profile as a living-doc room on pmoves.ai proper (not CF Pages): Remotion walkthrough (a2ui renderer) + PreTeXt technical panels + website/rooms design tokens, hosted behind the #2221 Traefik edge (public + optional forward-auth-gated panels). Scope-only — open decisions (host, PreTeXt vs MyST/Quarto, public-vs-gated, Remotion scope, DNS cutover) listed for sign-off before any build.
Companion to the ActivePieces Phase-1 stack (#2233).
🤖 Generated with Claude Code