Skip to main content

Versioned engineering knowledge hub

FeatureParent EpicDelivery statusStatus sourceOwnerApproved for Solution
3DARCH-FT-53DARCH-EP-1 — Engineering Platform, Quality, and OperabilityIN_BACKLOGEXACT3D Architecture Wizzard teamNo

Description​

Enable contributors and operators to maintain architecture, setup, authentication, rendering, and deployment guidance alongside source and publish it as a browsable static site.

User or operator problem​

Contributors and operators need one discoverable, versioned source for implemented architecture and operating guidance.

Expected value​

Keeps engineering knowledge reviewable with source and available as a browsable reference.

Scope​

Includes version-controlled engineering documentation authoring, build, navigation, indexes, sitemap, and implemented-versus-planned boundaries.

Exclusions​

  • End-user product behavior and solution or release authorization are outside these engineering Features.

Acceptance outcomes​

  • Contributors can author and preview version-controlled MDX documentation.
  • The knowledge hub builds through a root workspace command.
  • Static output contains navigable topic pages, indexes, and a sitemap.
  • Published guidance distinguishes implemented behavior from future intent.

Dependencies​

Risks​

  • Published guidance can confuse implemented behavior with future intent unless evidence boundaries remain explicit.

Human approval​

Linas approved this Feature for documentation on 2026-09-02T10:40:43.220Z. It is not Approved for Solution and has no implementation approval.

Delivery status evidence​

The Feature was separately registered at IN_BACKLOG as an accepted catalogue boundary. This records backlog retention, not design or delivery progress.

  • Event: Catalogue registration
  • Actor and authority: Linas — Human project team member
  • Reason: The Feature catalogue was accepted for governed documentation and retained in the backlog.
  • Status evidence

Architecture traceability​

  • Requirements: none derived.
  • Readiness: Not started.

Architecture solution work must not begin until a separate human Approved for Solution decision is recorded.

Tasks​

Review the Tasks group. No canonical implementation Tasks have been defined.

Original source​

Legacy implementation evidence​

The Feature boundary was mined from legacy revision c0ced47ecaf4426f47e5c2e4868677f7144b951a.