CCMForge Compose is the governed workbench for document engineering.
Build, validate, publish, and render HTML/PDF templates with Compose Workbench managing jobs, workspaces, approvals, and agent workflows while Compose Engine provides deterministic execution and render diagnostics.
Workbench control, engine execution.
Compose Workbench
The public product boundary for templates, jobs, validation, approvals, workspaces, and orchestration.
- Create and manage drafts, versions, and publish flow
- Track jobs, artifacts, approvals, and validation history
- Scope templates, policies, and operations by workspace
- Expose governed APIs for agent and automation use
Compose Engine
The internal deterministic runtime for preview, HTML, PDF, and diagnostics.
- Run deterministic template execution from explicit inputs
- Render semantic HTML as the canonical document form
- Generate PDF from the same composition path
- Return diagnostics and engine-coupled validation findings
Modern document workflows need more than a template editor.
Versioning, validation, publish controls, job history, and governed agent execution all belong in the same operational product instead of being scattered across tools and side channels.
Workbench as governed control plane
Jobs, workspaces, lifecycle, governance, validation orchestration, and agent operations live here.
Engine as deterministic execution
Preview, HTML, PDF, and render diagnostics stay isolated behind the internal compose boundary.
Validation and audit built in
Warnings, errors, approvals, and artifacts are part of the workflow instead of side channels.
Control the full document lifecycle.
Compose Workbench owns the workflow. Compose Engine owns execution. That separation keeps the product easier to govern, easier to test, and ready to evolve.
Create or update a draft
Keep document work inside a versioned lifecycle instead of scattered files and manual handoffs.
Validate before promotion
Run structural and accessibility checks and keep the findings linked to the template and job.
Publish with governance
Promote immutable versions through explicit review, policy, and approval boundaries.
Render with confidence
Delegate preview and production rendering to Compose Engine for deterministic execution.
Let agents assist without losing control.
CCMForge Compose is built for agent workflows, but deterministic rendering, lifecycle rules, and approval policy remain authoritative.
- Agent workflows operate through the Compose Workbench contract, not by bypassing lifecycle rules.
- Approvals and workspace policy stay in the loop where autonomy should stop.
- Artifact history, validation outcomes, and job state remain auditable.
- The orchestration layer is modular today so it can later move without breaking the product boundary.
Designed for traceability and speed.
CCMForge Compose is for teams that need deterministic output, accessible documents, governed APIs, and clear audit trails across the entire lifecycle.
- Teams building governed document-generation workflows
- Teams that need HTML and PDF output with traceable lifecycle controls
- Organizations where accessibility and validation cannot be an afterthought
- Agent-native operations that still need deterministic outputs and governance
Operational control without blurred boundaries.
Compose Workbench keeps lifecycle, validation, governance, and agent operations together while Compose Engine stays focused on deterministic execution.
- Workspaces isolate templates, jobs, approvals, and retained artifacts.
- Validation results stay linked to the document lifecycle instead of living in side channels.
- Publish flow, approvals, and agent actions remain governed and auditable.