Skip to main content

121 docs tagged with "reference"

View all tags

Api Reference

Service-layer API for the General Ledger Engine. All functions require a QueryContext for tenant-scoped execution.

Api Schema Alignment

Map the existing /api/v1/documents schema into relational tables and extend with compliance/ABAC fields.

Architecture Overview

CODITECT system design and component relationships - comprehensive overview of distributed intelligence architecture

Audit Trails Retention

Automate logging and lifecycle transitions so compliance is enforced "by default," not by convention.

BIO-QMS Document Inventory — Interim Tracker

Purpose: Master reference for all 104 artifacts in the CODITECT Biosciences QMS Platform data set. This document serves as an interim tracker to support writing the final 30-document-inventory and provides a clear, searchable catalog for both human review and agentic cross-reference.

Claude 4.5 Best Practices Guide

Complete reference for Claude 4.5 Sonnet capabilities including parallel tool calling, enhanced code exploration, and action policies

Document Detail Preview

The document detail view is a core screen - think of it as a "control panel" for one document.

Essential Metadata Fields

Most compliance capabilities should be driven by metadata, not paths. This document defines the minimum metadata fields required for HIPAA and FINRA compliance.

Finra Metadata Fields

FINRA Rule 4511 points to SEC Rule 17a-4 for how records must be made and preserved: accurate, complete, immutable (WORM or equivalent), and retained for specified periods.

Rbac Abac Mapping

This document explains how RBAC and ABAC attributes map to the PostgreSQL schema and how they're used for access control.

Scalable Index Schema

100K Markdown docs are moderate scale. A good design is "one indexed document per Markdown, plus structured fields for compliance filters."

Sped Mapping

Reference for SPED Escrituracao Contabil Digital (ECD) export, per IN RFB 2.003/2021.