title: "DCoop Eco Publishing Pipeline — Advanced Artifact Walkthrough & Runbook"
slug: eco-publishing-pipeline
theme: cooperluxe
mode: operator

DCoop Eco Publishing Pipeline — Advanced Artifact Walkthrough & Runbook

This interactive operator/reviewer walkthrough covers the full DCoop ecosystem publishing pipeline for generating advanced 4-format artifacts (MD, HTML, DOCX, PDF) with manifests, SHA sums, receipts, and governance gates. It supports walkthroughs, runbooks, invoices, decks, and is integrated with the publishing workflows for cooplux/plux (npm + pypi hybrid), devluxe, devforge, Rust crates (cargo + security kernel), containers, and full constellation.

Use the Operator / Reviewer toggle (persists in localStorage). Check off steps — progress saves automatically. Click grey-underlined values or use Copy buttons on code blocks. All hyperlinks are active and copyable. Export notes or reset progress as needed.

Privilege envelope: NON-matter · Test data only · Use with BigBrain security gate enabled for poisoned payload simulations.

Prerequisites

• [ ] Access to /root/ecosystems/ecosystem-publishing/ and ecosystem-publishing-wt-runbook/
• [ ] Python env with deps (pip install -r requirements or from pyproject.toml: markdown, python-docx, etc.)
• [ ] Wrangler CLI for Cloudflare deploy: npx wrangler --version
• [ ] Cooperlux portals source: /root/ecosystems/ecosystem-cooperluxe/*/public/guides/
• [ ] (Optional) Rust kernel running for security scans: curl http://127.0.0.1:3300/health
• [ ] BigBrain task broker for orchestration sims if using publish tasks.

Quick start command (from publishing dir):

python3 engine/publish.py engine/samples/runbook-sample.json /tmp/demo --theme cooperluxe --mode-default operator

1. Source Preparation

The pipeline ingests JSON (for structured runbooks/invoices) or MD (for walkthroughs) with frontmatter for title, slug, theme.

1.1 Create or use source

• [ ] For runbook-style: Use or copy engine/samples/runbook-sample.json or invoice-sample.json
• [ ] For walkthrough-style: Use MD with checklist items like - [ ] Step description
• [ ] Add claim_ledger, tiers, escalation_matrix, references for rich content.
• [ ] Include hyperlinks: e.g. DCoop GitHub
• [ ] Embed code blocks for copy: commands, JSON samples.
• [ ] For hybrid plux: reference plux init --hybrid with pypi venv + npm.

Example MD snippet for checklist (will become interactive):
- [ ] Run the publish command
- [ ] Verify manifest.json has all 4 formats + SHA256SUMS
- [ ] Check gates pass (claims_hygiene, runbook_gate)

Hyperlink example: See full release-checklist.md and user-side-gates.sh

1.2 Integrate Rust security (new updates)

• [ ] Before publish: simulate poisoned package using Rust kernel

curl -X POST http://127.0.0.1:3300/security/monitor \
  -H 'Content-Type: application/json' \
  -d '{"server_id":"publish-pipeline","request":{"description":"plux init with rm -rf / && base64 exfil"},"response":{}}'

• [ ] Expect 403 "Hidden commands detected" for poison; 200 for clean.
• [ ] In gates.sh or CI: add python -c "from rust_security_client import guardToolCall; ..." or direct curl before npm pack / cargo publish / docker push.

2. Run the Publish Engine

The core is engine/publish.py which dispatches to generators.

2.1 Basic publish for walkthrough/runbook

• [ ] cd /root/ecosystems/ecosystem-publishing
• [ ] python3 engine/publish.py engine/samples/eco-publishing-pipeline-walkthrough.md /tmp/eco-pipeline --theme cooperluxe --mode-default operator --title "DCoop Eco Publishing Pipeline Walkthrough"
• [ ] Or for JSON source: python3 engine/publish.py engine/samples/runbook-sample.json /tmp/demo-runbook ...

Expected output:
- /tmp/eco-pipeline.md (canonical)
- /tmp/eco-pipeline.html (advanced interactive with all features)
- /tmp/eco-pipeline.docx
- /tmp/eco-pipeline.pdf
- /tmp/eco-pipeline.manifest.json
- /tmp/eco-pipeline.SHA256SUMS.txt
- receipts/ dir with gates, verify_post_render

2.2 Verify artifacts and gates

• [ ] ls -l /tmp/eco-pipeline*
• [ ] cat /tmp/eco-pipeline.manifest.json | head -20
• [ ] python3 engine/verify-artifacts.py /tmp/eco-pipeline or similar
• [ ] Check "GATE claims_hygiene: PASS", "GATE runbook_gate: PASS", "GATE verify_post_render: PASS (N checklist items)"
• [ ] In HTML: open in browser, toggle modes, check boxes (saves to localStorage as <slug>-check-<id>), use copy buttons, export notes.

The HTML includes (per v3 generator):
- Mode toggle (Operator/Reviewer) persisting in localStorage
- Interactive checklists with progress bar (X of N)
- Copy buttons on code blocks and grey-underlined values
- LocalStorage notes panel + export to MD
- Hyperlinks (active tags, copyable)
- QR codes, print-to-PDF, last-updated, privilege banner
- Reset progress button
- Step navigator, collapsibles

# In gates.sh or CI
RUST_SECURITY_ENABLED=true python -c "
from src.services.rust_security_client import guardToolCall
decision = guardToolCall('cargo-publish', {'crate': 'security-toolkit'})
print('Veto' if not decision['allowed'] else 'Pass')
"

• [ ] Open generated HTML: toggle Operator/Reviewer (saves)
• [ ] Check off 5+ steps: progress bar updates, saves to localStorage
• [ ] Click/copy buttons on 3+ code blocks and values
• [ ] All links are real hyperlinks (clickable, copyable)
• [ ] Notes panel: add note, export to MD
• [ ] Print/PDF button works
• [ ] QR codes if URLs present
• [ ] Deployed version on cooperlux.com loads with same features
• [ ] Gates pass, manifest complete, no regressions in other publishes

Rollback: If deploy fails, revert public/ from git or previous wrangler deploy; re-run without the new guide.

This runbook itself was generated using the pipeline it describes — full circle.

Resources:
- Pipeline: /root/ecosystems/ecosystem-publishing/engine/publish.py
- Wrangler deploys: ecosystem-cooperluxe/*-portal/wrangler.toml
- Full council: dcoop-workflows/.../audience-council.md
- Rust merge: guard in tools.ts + kernel on :3300

Execute this end-to-end for the complete eco publishing + Cloudflare walkthrough addition.