Repository navigation
docs: align FlowForge architecture with the durable runtime - #16
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
There was a problem hiding this comment.
Sorry @mkarson1997, you've used your own review budget of 250,000 diff characters for the last 7 days.
You can request another review in 2 days and 1 hour by commenting @sourcery-ai review. Upgrade to get a review now.
|
Reviewer's GuideDocumentation is aligned with the implemented FlowForge durable runtime: the architecture now explains the in-process DAG and PostgreSQL-backed worker system with explicit invariants and delivery guarantees, while the README highlights engineering proof points and CI/security controls. No runtime behavior is changed. Sequence diagram for durable work claiming and recoverysequenceDiagram
participant Worker as DurableWorker
participant Queue as DurableWorkQueue
participant DB as PostgreSQL
participant Handler as TaskHandler
Worker->>Queue: register
Worker->>Queue: heartbeat
Worker->>Queue: claim work
Queue->>DB: acquire expiring lease
Queue-->>Worker: leased work
Worker->>Handler: execute task
alt task succeeds
Worker->>Queue: complete work
Queue->>DB: record terminal state
else worker disappears
Queue->>DB: reclaim expired lease
Queue->>DB: retry with row locking
end
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|



What changed
Why
FlowForge's implementation has moved beyond the old architecture document. The repository should describe what is actually implemented today and expose the strongest distributed-systems evidence clearly.
No runtime behavior changes.
Summary by Sourcery
Align the project documentation with the implemented durable runtime and make its distributed-systems guarantees and engineering controls explicit.
Enhancements:
Documentation: