Module status page

Architectural Render

Standalone render prompt/package/provider pipeline with adapter tests and production-image smokes, but no first-class route.

maturity: PARTIALproduction status: smoke testednavigation status: internalowner: Architectural render services and smokescapability owner: Architectural Render

What Is Live

  • Service: src/lib/architectural-render
  • Service: src/lib/architectural-render-adapter
  • Adapter: src/lib/architectural-render-adapter/adaptArchitecturalRenderForOs.ts

What Is Not Wired

  • Missing critical piece: First-class UI/API contract and artifact ownership boundary.
  • Missing adapter: Controlled route or studio adapter for production image generation.
  • Known risk: Large active work-in-progress set suggests architectural render is moving faster than OS integration.
  • Known drift: Standalone prompt modules may drift from feasibility/site program doctrine.
  • Duplicate logic: Program, layout, fuel, and site-specific prompts encode overlapping site constraints.

Known Blockers

  • medium: Standalone-heavy integration - Many render smokes and tests exist, but no first-class OS route is established.

Next Recommended Action

  • Finish render inventory separately and decide whether it is a studio module or a downstream feasibility artifact.

System Audit Evidence

  • Readiness score: 57%
  • Integration depth: adapter integrated
  • Route exposure: none
  • Security boundary: partial
  • Queue integration: wired
  • Readiness integration: partial
  • Workflow integration: partial
  • Data Room integration: not applicable
  • Export integration: partial
  • Test: src/lib/architectural-render/__tests__/auditArchitecturalRenderIntegrationReadiness.test.ts
  • Test: src/lib/architectural-render-adapter/__tests__/adaptArchitecturalRenderForOs.test.ts
  • Smoke: scripts/smoke-architectural-render-production-readiness.ts
  • Smoke: scripts/smoke-architectural-render-production-images.ts
  • Smoke: scripts/smoke-architectural-render-readiness.ts
  • Persistence: Render artifacts package output and provider artifacts.

Architecture Governance

  • 11 governance doctrines tracked
  • 15 required adapter seams
  • 13 forbidden direct couplings
  • No high or critical governance findings

Capability Registry

  • Read-only Architectural Render status page for prompt tooling and integration readiness.
  • Registry production status: internal only
  • Primary nav group: Intelligence
  • Capability: system audit maturity
  • Capability: render evidence inventory
  • Capability: not-wired route gap
  • Capability: safe related links

Related Links

Safe Available Actions

No mutation controls on this page. This page does not mutate readiness, auto-approve obligations, execute workflow actions, advance stages, send emails, or create default/breach conclusions.