Documentation

The Portal explains the engineering record without exposing the private workshop.

DoricDev follows Documentation-as-Code and Evidence-as-Code. This public gateway explains what the authoritative records cover, why they matter and how they support product delivery.

Recommended reading path

Start with the platform, then follow the evidence.

This sequence mirrors the Platform reading model while keeping the public journey focused on useful context rather than repository structure.

01Platform overview
02Engineering standards
03Studio operating system
04Engineering evidence and economics
05Design and brand standards
06Platform releases and evidence reports

Engineering sources

Curated understanding, authoritative records.

Each card describes an authoritative engineering source. Private repositories remain private; the Portal presents their purpose and current relevance without creating inaccessible links.

Purpose, philosophy, capabilities and product-consumption model for DoricDev Platform v1.

Purpose: Understand what the Platform owns and how products consume it.
Authoritative source: doricdev-platform/README.md

Maintained in the private engineering record.

Architecture, repository strategy, security, licensing and shared engineering guidance.

Purpose: Provide the baseline for consistent, maintainable product engineering.
Authoritative source: doricdev-platform/docs/engineering

Maintained in the private engineering record.

DSOS v1.2, Conversational Engineering and the foundations for Studio Intelligence.

Purpose: Explain how DoricDev plans, steers, executes and learns from initiatives.
Authoritative source: doricdev-platform/docs/studio

Maintained in the private engineering record.

Evidence-as-Code, quantitative engineering evidence, value engineering and engineering economics.

Purpose: Connect delivery activity to traceable outcomes, value and reusable capability.
Authoritative source: doricdev-platform/docs

Maintained in the private engineering record.

Colour, typography, spacing, geometry, certified SVG masters and production asset guidance.

Purpose: Keep every DoricDev product visually coherent without recreating the brand.
Authoritative source: doricdev-platform/docs/design

Maintained in the private engineering record.

Release history, Engineering Evidence Reports and executive-facing delivery updates.

Purpose: Record what changed, why it matters, what value was created and what should happen next.
Authoritative source: doricdev-platform/docs/releases

Maintained in the private engineering record.

Architecture and technical direction for this reference implementation of Platform v1.

Purpose: Show how a product maps Platform standards into a working implementation.
Authoritative source: doricdev-portal/docs/architecture.md

Maintained in the private engineering record.

Portal delivery history and current release-candidate evolution.

Purpose: Maintain a product-level record alongside the Platform evidence model.
Authoritative source: doricdev-portal/docs/release-notes.md

Maintained in the private engineering record.

Documentation-as-Code

Record decisions alongside delivery.

Standards, architecture and release records evolve with the product instead of becoming detached documents that quickly lose context.

Evidence-as-Code

Explain what changed and why it matters.

Engineering evidence connects implementation to outcomes, economics, value, learning and future opportunity.

Explore next

See how engineering records become an operating model.

The Studio shows how DoricDev turns delivery records into evidence, value and better future decisions.

Studio Platform