You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit da643fb
Browse filesBrowse the repository at this point in the historyBrowse files
Present KeyLoad as an AI-native database across README and landing
README: lead with the AI-native thesis ("Agents shouldn't need a dozen
databases"), a before/after stack diagram, why we think one database is
the future, a capability matrix (atomic writes, reads, SQL, MCP tools per
model), composition and agent tool-call diagrams, why .NET, Orleans and
ZoneTree, an SEO-oriented FAQ and calls to action. All credits are kept;
the benchmark comparison engines are now credited too.
Landing: add the same theses in a "Why an AI-native database" section and
a "Why .NET, Orleans and ZoneTree" section with Liquid Glass styles, plain
product language for composition and engine copy, a valid MCP request
sample, a Get started CTA, and AI-native title, description, Open Graph
and JSON-LD within the AC-SEO-002 contract.
Traceability: REQ-COMP-007 / AC-COMP-009 / ADR-067 stage 8 (TASK-COMP-008)
with SiteProductThesisTests (README headings, landing main copy,
forbidden claims, all-missing and one-missing cases). Shared
SiteProductCopy helper replaces duplicated parsing, and README and
landing now assert one set of composition stage contracts.
Verification: three review rounds (accuracy, engagement/SEO, final gate)
with all findings applied; SiteTests Release build and dotnet format pass;
thesis and composition assertions verified statically with the tests' own
tokens; Mermaid diagrams render; landing checked at 320/375/761/1440 px
with no overflow. The site suite needs the GitHub exact-revision gate and
was not run locally.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@@ -81,6 +82,7 @@ one request grain; physical hosts retain ZoneTree/native WAL and RF3 ownership.
81
82
| AC-COMP-006 | One cumulative read-byte budget and expanded MaxBatchMutations bound cover entire batch; overflow rejects all, never truncates silently; reads materialize before writes; replicated derivation uses deterministic bounds without local wall deadlines/cancellation | byte/count/multiple-composition/exact-cap/replica-determinism cases; code review of callbacks and apply clock |
82
83
| AC-COMP-007 | Native DTOs have stable aliases/IDs; public polymorphic JSON preserves old shapes; SQL canonical CALL needs no second gateway/operation kind; fresh request routing remains | serializer roundtrip + frozen pre-composition native writer fixtures + SQL compiler + actual RF3 .NET/official MCP forward/reverse/retry/error tests |
83
84
| AC-COMP-008 | Build/formatter/governance and relevant TUnit tests pass; exact-source Actions full normal/scalar/recovery/RF3 remain separately recorded, website publication requires existing complete Benchmarks pipeline | retained source/SHA/commands/reports in implementation receipt; no numeric coverage claim without collector |
85
+
| AC-COMP-009 | README and landing both state the same theses: KeyLoad is an AI-native database; agents shouldn't need a dozen databases; why we think one database is the future; why .NET, Orleans and ZoneTree. Neither surface claims production readiness. README theses are its section headings and lead sentence, not navigation links; landing theses are visible `<main>` copy, not metadata. Fail if either surface drops a thesis or matches the forbidden-claims pattern | SiteProductThesisTests (README headings, landing main copy, forbidden claims on both, all-missing and one-missing cases); prose and SEO review is the explicit manual exception |
84
86
85
87
Frozen DTOs: QueueGraphLink(From EntityRef, To EntityRef, Label string,
<li><spanclass="step-no" aria-hidden="true">01</span><div><h3>Queue to knowledge graph</h3><p>Read ready messages, resolve their linked entities and write knowledge-graph relationships inside the database.</p></div></li>
171
171
<li><spanclass="step-no" aria-hidden="true">02</span><div><h3>Graph to queued actions</h3><p>Follow visible relationships to enqueue actions carrying canonical entity references.</p></div></li>
172
-
<li><spanclass="step-no" aria-hidden="true">03</span><div><h3>One authorized atomic command</h3><p>Source and target resources share the same atomic partition and transaction domain. A failed effect rolls back the whole command. Projection does not lease or ACK messages. Blobs remain part of the same database; staged upload and publication use their existing operations outside this initial graph/queue batch.</p></div></li>
172
+
<li><spanclass="step-no" aria-hidden="true">03</span><div><h3>One authorized atomic command</h3><p>Every source and target must live in the same atomic partition and transaction domain, so the whole command succeeds or rolls back together. Reading a queue into the graph does not lease or ACK its messages. Blobs remain part of the same database, but use their separate upload and publication operations.</p></div></li>
<p>The source adds this initial bounded procedural composition stage through SQL CALL, the .NET SDK and official MCP, with exact-source qualification pending. Full declarative SQL, the native SQL-client protocol and cross-partition composition remain required and pending.</p>
185
+
<p>The current composition API runs through SQL CALL, the .NET SDK and the official MCP server. KeyLoad is a development preview: full declarative SQL, the native SQL-client protocol and cross-partition composition are still in development, and production guarantees remain under qualification.</p>
0 commit comments