How To Bootstrap HASMaster In Paperclip

Create a first-phase Paperclip operating model for HASMaster that matches the real state of the project: the website and content platform are nearly production-ready, the scenario workflow model already exists, the agent roster is already defined, and video and YouTube operations still need tool and process buildout.

Company

Create one company: HASMaster.

Suggested company goal:

Guide people through the full automation lifecycle with privacy-first design, operation, and maintenance; turn real automation solutions into structured content; and grow HASMaster through the platform, the scenario pipeline, and the HASMaster_1000 media engine.

Projects

1. Strategy and Business: monetization, KPI definition, vendor strategy, launch sequencing, and business model decisions.
2. Platform and Site: WordPress staging readiness, theme and plugin release readiness, journeys, assistant UX, and documentation and publishing operations.
3. Scenario Pipeline: one parent issue per scenario, child issues for WF-200-01 through WF-200-03, and Paperclip visibility fed by LangGraph and n8n when needed.
4. Production Tools: video and YouTube operating system buildout, Google tooling, asset handling, publishing, and media storage.

Agents

1. Executive Showrunner
2. COO
3. Project Manager
4. Writer
5. Editor
6. QA Engineer
7. Documentation Librarian

Use the Librarian as a first-phase agent, not a later cleanup role.

What Not To Create As Permanent Agents Yet

Do not create long-lived Paperclip agents for workflow functions such as device-research, documentation, evaluation-scorer, wordpress-publisher, or journey stages like get-inspired, setup, or automate. Model those as issues, child issues, or workflow runs instead.

Librarian Operating Rule

1. Check runtime truth in /mnt/hasmaster_1000 and /mnt/nas_docker_apps.
2. Update canonical local docs under /mnt/nas_docs.
3. Update staged published guides when the change affects operator-facing or public-facing guidance.
4. Keep local docs and staged published material in sync.

Approval Rule

Apply the Home Lab approval policy to this bootstrap.

• Creating or updating the first-phase Paperclip structure is pre-approved when you ask for it.
• Documentation updates and staging guide alignment are pre-approved parts of the same workflow.
• Release, publish, production cutover, and destructive rollback remain explicit actions.
• Operational credentials belong in 1Password, not in docs or temporary session state.

Skills And MCPs To Use First

Prioritize Documentation Librarian with the documentation-librarian, manual-librarian, hasmaster-prod-retrieval, and hasmaster-publish skills plus the docs, doc-mcp, cms-wordpress-staging, and data-weaviate MCPs. Use Project Manager with portainer, sys-api, and playwright. Use QA Engineer with ha-mcp, playwright, portainer, and sys-api. Use Writer and Editor with docs, cms-wordpress-staging, and playwright. Use COO and Executive Showrunner with docs and data-weaviate.

First Week Plan

1. Create company HASMaster.
2. Create the four projects in this guide.
3. Create the seven durable agents in this guide.
4. Add the initial issues listed under each project.
5. Create one real scenario parent issue plus the three workflow child issues in Scenario Pipeline.
6. Use Documentation Librarian to update local docs and staged guides as you refine the operating model.
7. Only after the board feels natural, wire more automation into the Paperclip bridge.

Current Live Seed Status

As of 2026-04-02, this model has been applied to the live HASMaster Paperclip company.

• The four first-phase projects exist.
• The seven durable agents exist.
• The starter issue set exists across strategy, platform, scenario, and production tools.
• The first SCN-001 parent issue and the WF-200-01 to WF-200-03 child issues exist.
• The original onboarding project was archived and its starter issue was cancelled.
• The Librarian alignment issue was added so docs and published guides remain part of the operating model.

Next Step

After the first-phase model is live, move to the HASMaster scenario pipeline guide and wire the LangGraph and n8n status bridge so Paperclip reflects real workflow state.