Skip to content

Latest commit

 

History

History
157 lines (150 loc) · 14.9 KB

File metadata and controls

157 lines (150 loc) · 14.9 KB

Каталог архітектурних рішень

KeyLoad — одна composable база для AI agents: документи, таблиці, графи, пошук, time series, blobs, черги та події поєднуються через авторизовані SQL, SDK і MCP операції. Orleans виконує кожен запит через окремий request grain; node-local PartitionHost володіє ZoneTree, журналами та ordered apply gate. Початкова production topology — RF3, orchestration і тести належать Aspire.

ADR-116 і CurrentFormat визначають єдиний поточний формат. ADR-011 зберігає повний контракт його recovery, backup та restore. ADR-017 визначає session tokens і native ownership movement. Невідомі або пошкоджені формати відхиляються до ефектів.

Поточні shared contracts: Orleans primitives, typed runtime options, TimeProvider, functional coverage, MCP discovery та independent Website publication. Build and Tests, Benchmarks, Website і Release мають окремі workflows.

Accepted означає прийнятий контракт, а не виконані acceptance-критерії. Proposed означає невирішений вибір, який не можна рекламувати як готову capability. Кожен ADR містить REQ/AC, ownership, ordered implementation, tests і verification; feature specifications та implementation status містять повну traceability. Номери рішень стабільні; каталог містить лише наявні активні ADR.

flowchart LR
    Policy[Owner policy and feature requirements] --> Decision[Current architectural contract]
    Decision --> Ownership[Exact slice ownership and join points]
    Ownership --> Operations[Whole operation implementation and tests]
    Operations --> Proof[Source bound Linux qualification]
    Proof --> Status[Honest acceptance status]
Loading

Активні рішення

Рішення Статус контракту
ADR-001: Atomic partition identity and affinity Accepted
ADR-002: Command identity and persisted idempotency Accepted
ADR-003: Durability profile and acknowledgement barrier Accepted
ADR-004: Committed read views and pagination cuts Accepted
ADR-005: Canonical namespaces and ordered key codec Accepted
ADR-006: Strict synchronous indexes and derived projections Accepted
ADR-007: Orleans replica consensus and metadata bootstrap Accepted
ADR-008: Backup cuts and independent log retention Accepted
ADR-009: Search provider and projection boundaries Accepted
ADR-010: Bounded query execution and security barriers Accepted
ADR-011: Current native format and restore authority Accepted
ADR-012: Versioned KeyLoad SQL subset Accepted
ADR-013: One authorized query AST across interfaces Accepted
ADR-014: Persisted principals, scoped RBAC, and row policy Accepted
ADR-015: Sensitive-data omission, use, and lineage Accepted
ADR-016: Atomic partitions packed into physical shards Accepted
ADR-017: Commit and session tokens across ownership movement Accepted
ADR-018: Global per-modality windows and weighted rank fusion Proposed
ADR-019: Managed-first ANN provider qualification Accepted
ADR-020: Independent bounded query contexts Accepted
ADR-021: Comparable PostgreSQL performance baseline Accepted
ADR-022: Policy epoch reauthorization at request and page boundaries Accepted
ADR-023: Separate lifecycle and authority for journals, events, CDC, and queues Accepted
ADR-024: Catalog-bound shared TransactionDomain Accepted
ADR-025: Stream revisions and stable per-atomic event-feed positions Accepted
ADR-026: At-least-once delivery with fenced leases and inbox effects Accepted
ADR-027: Durable consumer groups with contiguous checkpoints Accepted
ADR-028: Persisted scheduling with logged evaluation time Accepted
ADR-029: Event and message classification with safe diagnostics Accepted
ADR-030: Retention pins and paused restore of an older cut Accepted
ADR-031: Modular all-in-one deployment with reserved control resources Accepted
ADR-032: Preserve existing policy while adopting MCAF Accepted
ADR-033: source-owned code quality and evidence gates Accepted
ADR-034: Reproducible Docker cluster comparisons and GitHub result graphs Accepted
ADR-035: bounded operation work and resource lifetime Accepted
ADR-036: Orleans foundation and client-driven qualification Accepted
ADR-037: Повний каталог функцій і архітектурних рішень Accepted
ADR-038: Canonical chunked BlobStorage and bounded reads Accepted
ADR-039: Official MCP SDK і agent access до canonical operations Accepted
ADR-040: Static product website, conceptual Three.js and qualified evidence Implemented
ADR-041: read-only public collections with stable wire bytes Accepted
ADR-042: explicit command admission and inbox resource ownership Accepted
ADR-043: comparative harness library and executable host Accepted
ADR-044: immutable comparative harness contracts Accepted
ADR-045: Owned PostgreSQL comparison schemas and constant commands Accepted
ADR-046: Cohesive node-local storage owners under numeric gates Accepted
ADR-047: public embedded benchmark scenarios and typed executable Accepted
ADR-048: bounded owned storage metadata Accepted
ADR-049: Genuine Neo4j harness and acknowledged cleanup ownership Accepted
ADR-050: Isolated TimeSeries and Timescale comparison profile Accepted
ADR-051: same-origin read-only administration console Accepted
ADR-052: bounded TimeSeries latest and raw aggregates Accepted
ADR-053: one light KeyLoad visual identity for the console and the site Accepted
ADR-054: Central SQL over canonical database operations Accepted
ADR-055: Typed relational rows in canonical entity storage Accepted
ADR-056: Isolated Linux comparison cells and complete evidence aggregation Accepted
ADR-057: Native Orleans binary atomic WAL Accepted
ADR-058: Orleans-coordinated disposable cache memory Accepted
ADR-059: separate native intensive TimeSeries family Accepted
ADR-060: generated native internal serialization Accepted
ADR-061: bounded node-owned replica term metadata Accepted
ADR-062: Workflow responsibility and qualification boundaries Accepted
ADR-063: bounded callback-free database phase profiling Accepted
ADR-064: Four workflows and source-bound release delivery Accepted
ADR-065: Full SQL syntax and client protocol Accepted
ADR-067: One composable database for AI agents Accepted
ADR-068: Native benchmark gate repair Accepted
ADR-069: Representative scaled workload qualification Accepted
ADR-071: Canonical ZoneTree storage and full-text providers Accepted
ADR-072: Authorized SQL event and queue read views Accepted
ADR-073: Logged bounded time-series retention Accepted
ADR-074: One Aspire-owned test entry point Accepted
ADR-075: Bounded aggregate snapshots and pure replay Accepted
ADR-076: Publish only the complete current comparison cohort Accepted
ADR-078: Bounded native full-text candidate generations Accepted
ADR-079 — Bounded lossless time-series chunk codec qualification Accepted
ADR-080: Isolate benchmark failures during publication Accepted
ADR-081 — Awaited bounded native search execution Accepted
ADR-082 — Native Orleans CQRS streams Accepted
ADR-083 — Bounded native CQRS HTTP consumption Accepted
ADR-085: Visible bounded native benchmark progress Accepted
ADR-086: Stop owned test workloads on terminal Aspire failure Accepted
ADR-087: Filtered retrieval in the authorized search cut Accepted
ADR-088: Durable remote queue intent and receipt Accepted
ADR-089: Canonical guarded vector projection lineage Accepted
ADR-090: Same-cut graph scope, retrieval and expansion Accepted
ADR-092: Logged-time recurring occurrences and saga timeout CAS Accepted
ADR-093: Compare-and-set resource field policies Accepted
ADR-094: Orleans coordination of canonical recurring and saga due work Accepted
ADR-095: Bounded native index generation leases and retirement Accepted
ADR-096: Bounded comparable global modality windows before fusion Accepted
ADR-097: Provider-owned native read-cut leases Accepted
ADR-098: Bounded authorized shortest paths Accepted
ADR-099: RF3 physical shard catalog foundation Accepted
ADR-100: Internal bounded Q1 merge across local atomic partitions Accepted
ADR-101: Explicit atomic-partition placement directory See decision
ADR-102: Same-owner cross-partition graph edge delivery Accepted
ADR-103: Bounded scaled database comparison stage Accepted
ADR-104: Native ManagedCode gateway and graph-based MCP discovery Accepted
ADR-105: Published NuGet dependency refresh Accepted
ADR-106: Fenced movement of a complete atomic partition between physical owners Accepted
ADR-107: Elastic License 2.0 Accepted
ADR-108: Typed synchronization and Orleans state ownership Accepted
ADR-109: Native vector qualification and additional comparison databases Accepted
ADR-110: native Orleans execution and scheduling primitives Accepted
ADR-111: Semantic rules for magic runtime values Accepted
ADR-112: Independent Website publication with optional benchmarks Accepted
ADR-113: General runtime literals and centralized typed options Accepted
ADR-114: verified backup artifact publication Accepted
ADR-115: TimeProvider ownership Accepted
ADR-116: one current format before the first release Accepted
ADR-117: native TUnit CI entry Accepted
ADR-118: bounded typed-row INNER JOIN Accepted
ADR-119: TUnit-owned local membership image Accepted