Skip to main content

Technical docs

Documentation index for asset review.

A curated map of public references and review-only materials. Use it to find available docs and request the right packet for a specific asset.

Doc access

Buyers can see the doc inventory before requesting access.

This page is a map, not an unlocked data room. It separates public references from internal or NDA-only artifacts so reviewers understand what is available.

9

Active refs

9

Public refs

3

Controlled refs

Public docs support orientation without exposing sensitive materials.
Internal and NDA-only entries stay visible as diligence inventory, not self-service access.
Only public entries link to GitHub; controlled entries route to the diligence request path.
Status labels distinguish current references from historical context and needs-review materials.

3 references

Setup and Architecture

Core references for local setup, stack constraints, and repository structure before implementation work.

ActivePublic

Local Setup

Environment setup, dependency install, and troubleshooting guidance for contributors.

Path: docs/LOCAL_SETUP.md

Audience: Frontend, backend, and platform engineers

Updated: May 2026

View public GitHub doc
ActivePublic

Tech Stack

Framework versions and architectural constraints for Next.js, React, TypeScript, and tooling.

Path: docs/TECH_STACK.md

Audience: Engineers and technical reviewers

Updated: May 2026

View public GitHub doc
ActivePublic

Architecture

Repository structure, content/data flow boundaries, and implementation patterns.

Path: docs/ARCHITECTURE.md

Audience: Engineers and buyer diligence reviewers

Updated: May 2026

View public GitHub doc

4 references

API and Integration Standards

Contracts and error semantics used for route development, plus diligence integration implementation context.

ActivePublic

API Design

Route naming, request/response envelopes, validation, and error handling conventions.

Path: docs/API_DESIGN.md

Audience: API engineers and integration reviewers

Updated: May 2026

View public GitHub doc
ActivePublic

API Error Codes

Canonical error-code matrix and route-specific failure conditions.

Path: docs/API_ERROR_CODES.md

Audience: API engineers and frontend integrators

Updated: May 2026

View public GitHub doc
Needs ReviewNDA Only

Diligence Implementation Quickstart

Scaffold implementation steps for DocuSign and ShareFile flow hardening.

Path: docs/DILIGENCE_IMPLEMENTATION_QUICKSTART.md

Audience: Platform and integration engineers

Updated: May 2026

Request doc access
Needs ReviewNDA Only

Diligence Flow Integration

Buyer request to data-room sequence and integration boundaries for diligence workflows.

Path: docs/DILIGENCE_FLOW_INTEGRATION.md

Audience: Buyer workflow and API owners

Updated: May 2026

Request doc access

5 references

Operations and Quality

Current status, workflow standards, and auditing references used for release readiness and quality reviews.

ActivePublic

Status Snapshot

Current completed milestones, open objectives, and known blockers.

Path: docs/STATUS_SNAPSHOT.md

Audience: Product owners and implementation leads

Updated: 2026-05-14

View public GitHub doc
ActivePublic

Workflow

Task-oriented implementation SOPs and session closeout expectations.

Path: docs/WORKFLOW.md

Audience: Contributors and maintainers

Updated: May 2026

View public GitHub doc
ActivePublic

Accessibility

WCAG 2.1 AA guidance, interaction patterns, and validation checks.

Path: docs/ACCESSIBILITY.md

Audience: Frontend engineers and QA reviewers

Updated: May 2026

View public GitHub doc
HistoricalInternal

Architecture Content Audit (2026-05-13)

Route-level reconciliation audit with remediation punch list and acceptance criteria.

Path: docs/ARCHITECTURE_CONTENT_AUDIT_2026-05-13.md

Audience: Technical leads and release managers

Updated: 2026-05-13

Request doc access
ActivePublic

Content Inventory (2026-05-13)

Canonical app inventory, source-of-truth rules, and content guardrails.

Path: docs/CONTENT_INVENTORY_2026-05-13.md

Audience: Content and product stakeholders

Updated: 2026-05-13

View public GitHub doc

Need a focused packet?

Start public, then request app-specific technical materials.

Public references help reviewers orient quickly. Deeper architecture, source, data handling, testing, and transfer notes are shared through the controlled diligence path.