admin/stargue-publishing-engine
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
1dc1a1a07a06f4bc61c0039b138d9faaeb0e072e
stargue-publishing-engine/docs/deferred-gates.md
Angelo B. J. Luidens 1dc1a1a07a Stage 0: governance scaffolding + monorepo bootstrap 
Phase 1 foundation for the Stargue Publishing Engine (plan v2, BMAD
panel-reviewed 2026-04-19 — 1 APPROVE, 6 REVISE, 0 REJECT; all principles >=3).

- Governance doctrine adopted from DQMS
  (.clinerules/12-foundational-principles.md,
  .claude/hooks/gate-plan-exit.sh, .claude/skills/bmad-plan/SKILL.md)
- Bun workspaces + Turbo; apps/{mcp-linkedin,scheduler,admin};
  packages/{schema,sanitize,linkedin-client,observability}
- Drizzle schema (content, publications, approvals, metrics,
  linkedin_tokens, audit, outlet_feature_flags) with idempotency_key
  UNIQUE and kill-switch table per TEA/dev panel revisions
- LinkedIn API canon: Posts API /rest/posts (not legacy UGC); OAuth
  auth-code without PKCE; secretbox (not sealed-box); Community
  Management API as separate approval gate from MDP
- Frontmatter Zod schema (status, language, outlets[], sanitize,
  scheduled, version)
- Pino observability with PII redaction
- Expand-then-contract migration runbook
- Plan + panel verdicts mirrored to docs/plans/
- Deferred gates logged (Dokploy PaaS verification, LinkedIn Dev
  Portal app registration)

bun install + bun run typecheck both exit 0 across 11 workspaces.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-04-19 07:22:07 -04:00

2.1 KiB
Raw Blame History

Deferred gates

Items that could not be completed in the Stage 0 execution window and must be resolved before the gate they block.

Gate 0.8 — Postgres + Redis on PaaS

Status: Deferred 2026-04-19. Reason: Dokploy MCP tools (mcp__dokploy__*) were not loaded in the Stage 0 session, and DOKPLOY_API_KEY was not in the WSL environment. Direct API query not possible in-session. Blocks: Stage 2 (database + API) — the scheduler and admin cannot run without a Postgres + Redis pair. Resolution options:

  1. Recommended: Restart Claude Code with the vault's .mcp.json Dokploy MCP attached; run mcp__dokploy__list_applications / equivalent against sg-paas-s1.stargue.net to verify or provision.
  2. Angelo confirms via Dokploy web UI and reports service names + connection hostnames.
  3. Provision fresh Postgres + Redis services in the stargue-publishing-engine Dokploy stack (clean room; isolates blast radius from other PaaS apps).

Acceptance when resolved: this file updated with service names, hostnames, and connection-string env-var locations (Dokploy secrets).

Gate 0.9 — LinkedIn Developer Portal apps

Status: Pending Angelo's manual action. Reason: Dev Portal registration cannot be automated — requires human auth at linkedin.com/developers/. Blocks: Stage 3.1 (OAuth flow) live integration — structure + contract tests can proceed in parallel. Resolution: follow the checklist in linkedin-apps.md. Expected time ~30 min for OIDC + Share; multi-week for Community Management API + MDP partner approvals. Acceptance when resolved: linkedin-apps.md registry filled in with app IDs; client credentials stored in Dokploy secrets LINKEDIN_CLIENT_ID, LINKEDIN_CLIENT_SECRET, LINKEDIN_TOKEN_ENCRYPTION_KEY.

What proceeds in parallel

Stages 1–2 (local DB), 3 structural (OAuth code + tool shapes + msw fixtures), 4 (scheduler), 5 (admin UI with Authentik stub), 6 (sanitize integration in stargue-com/.net), 7.1 (/market audit baseline), 7.2 (7 Cs post drafting) can all proceed without these gates. Live integration tests and first production publish require both gates resolved.