Repository navigation
Folders and files
| Name | Name | Last commit date | ||
|---|---|---|---|---|
Repository files navigation
Concord License: GNU Affero General Public License v3.0 or later (/LICENSE) Concord is an AP distributed system, a runtime and coordination layer designed for robotic fleets. It gives you highest reliability from warehouse aisles to mines, factories, and space. It is a fleet brain that coordinates the fleet, not a real-time controller. Motor, collision, and sensor loops run at the edge. Tested with a proprietary simulation suite. It is the primary way we validate partition, reunion, and scheduling. Scope Concord is consolidated, not expanding. Noise IK over :8443 is the only transport and no others will be added. All work goes inward: correctness, reliability, verification, and optimization of what is already here. No new surface, fixes only. The bar, same for every change: externally identical behavior. Optimization needs a measurement before and after, not a hunch. Replacement needs the same wire format, CLI surface, and journal semantics, proven by the existing gate plus a Resonance run, not by reading the diff. Fixes need a failing gate first, then the smallest patch that turns it green without moving any other number. Cleanup needs the full gate green on both sides; elegance in the diff proves nothing. Anything adding a flag, a verb, or a field is expansion, and the answer is no until the freeze lifts. Scale Density caps, not headcount. Keep mutually reachable clusters near tens, near 25 per radio cell. Movers carry omnis at 2-3 dBi, stock link holds hundreds of meters with margin. Airtime fails before protocol does. Spread is epidemic: one reachable member hands over the mesh, gossip repeats to random peers, and journal union carries unknown events through intermediaries. One cell holds near 25 active omnis; past 30 contention grows, past 60 split cells. Sessions pool to 60 s, so handshakes amortize near 1 per 12 ticks. Calc: N=60 averages 59x15 ms / 12 about 74 ms per 5 s tick on handshakes plus 59 short pulls and gossip. Airtime still caps cells before protocol caps segments. Tables live in docs/scaling and docs/radio. Documentation Overview - /docs/overview Architecture - /docs/architecture Noise Transport - /docs/noise Journal Sync - /docs/cursors Metrics and Pressure - /docs/metrics Position Trail - /docs/trail Files - /docs/files Devices - /docs/devices Nodev: filesystems that forbid devices - /docs/nodev Startup Order - /docs/startup QoS - /docs/qos Health Checks - /docs/health Scaling - /docs/scaling Radio Planning - /docs/radio IPC Reference - /docs/ipc CLI Reference - /docs/cli Go SDK Reference - /docs/sdk Deployment Guide - /docs/deployment Regression Suites - /rsuite/README Contributing Concord takes no pull requests. Propose first, patch second, both by email to contact@podomy.com. 1. RFC: send a request for comments describing the problem, the approach, and why it stays inside the scope above. Wait for agreement before writing any code. 2. Patch: build the change as commits following /COMMITS, export them with git format-patch, and send them with git send-email. That mailed diff is the change; there is no PR queue behind it. Announcements and engineering updates on distributed systems, consensus algorithms, and robotic fleet coordination are shared via our newsletter at https://podomy.com. Commit message format - /COMMITS Contributor license agreement - /CLA Contributing - /CONTRIBUTING License Concord is distributed under the GNU Affero General Public License v3.0 or later. See /LICENSE.