diff --git a/site/architecture.html b/site/architecture.html new file mode 100644 index 0000000..c64b4b3 --- /dev/null +++ b/site/architecture.html @@ -0,0 +1,98 @@ + + + + + + Architecture | fkst + + + + + + +
+ + +
+
+

Company model

+
+

+ Work is modeled as Company, Department, and Person. A company owns + the durable graph, departments declare concrete responsibilities, + and persons are spawned workers that execute bounded tasks. +

+
    +
  • Sources raise events from outside facts such as GitHub issues or timers.
  • +
  • Fanout gives multiple departments the same fact without runtime interception.
  • +
  • Routing selects the next department, spawn creates work, and RAISED records the resulting events.
  • +
+
+
+ +
+

Reliable delivery

+
+

+ Delivery is redb-backed and treats retries as normal operation: + events are delivered at least once until acknowledged, leases and + fencing keep workers from racing stale ownership, and DLQ records + preserve failures for inspection. +

+

+ Large content does not ride inside reliable payloads. Payloads + carry a source_ref pointer plus small control fields, and + consumers re-fetch the authoritative content when they need it. +

+
+
+ +
+

Repository ecosystem

+
+

+ The ecosystem is split into three public repositories. The + fkst-substrate repo owns the engine and package contract, + fkst-packages owns reusable package patterns, and fkst-website + adds only website-domain Lua behavior. +

+

+ Packages can be flat or composed. A composed package references + dependencies through declared composition, and the engine receives + one graph by unioning the pinned package roots supplied at runtime. +

+
+
+
+
+ + + + diff --git a/site/doctrine.html b/site/doctrine.html new file mode 100644 index 0000000..37225bd --- /dev/null +++ b/site/doctrine.html @@ -0,0 +1,92 @@ + + + + + + Doctrine | fkst + + + + + + +
+ + +
+
+

Markers are facts

+
+

+ GitHub is eventually consistent, so fkst writes marker records as + facts and uses version-CAS style claims around them. The marker is + not decorative metadata; it is the observable state a later worker + can read, compare, and advance. +

+
+
+ +
+

Gates judge pipelines

+
+

+ Gates are codex-judgment pipelines over the work product and + evidence. They are not per-event human labels sprinkled through + the queue. The review is explicit, repeatable, and tied to the + proposal or delivery stage being judged. +

+

+ Write posture is also explicit. The website package has one host + environment fact for publishing: FKST_SITE_WRITE=1 enables real + writes, and missing publish configuration fails closed. +

+
+
+ +
+

One current shape

+
+

+ fkst does not keep backward-compatibility modes, deprecated + shims, or speculative branches in the system. When the contract + changes, the current shape changes with it. +

+

+ New patterns must serve a proven present problem. The bias is to + keep the runtime and packages small enough that every visible + mechanism earns its place. +

+
+
+
+
+ + + + diff --git a/site/index.html b/site/index.html index 8233c8a..0aff3ce 100644 --- a/site/index.html +++ b/site/index.html @@ -14,6 +14,8 @@