Date: 2026-10-08 Status: 3nov, implemented mostly, what's left is polish, more ui exposure, making it into a nice user feature, actually using it, getting data from own usage, perfecting it. pre-0.9.0-polish-blocker
"the feature i am imagining is called comet"
"if QNTX is heaven" "and ground is here, as in earth" "Comets are what slowly creates a body in space, like earth, right?"
The node builds ground, and the build lands on the machine ground runs on.
[[ADR-027-Permissions]] 27-2 waits on this.
Normally, ground is compiled where it executes:
make installIts SessionStart asks GitHub for the latest tag once a day and tells the session when a newer one exists.
"Tailored to that repository ground project .pbt specifies,
It has CTFE-able material, for example:
control:
We can still have super fast hooks. Even faster when the builds are done by QNTX as Comet "
git ls-files (ground tools/wind.d)."I dont know if i will be able to build a D program for mac M1 on a lightsail box"
nix shell at nice 19, one build at a time.cc -target <triple> and adds
-lpthread -lm -lobjc; it reads no SDK and no sysroot (ldc
driver/tool.cpp, driver/linker-gcc.cpp). With -betterC it links no druntime
and no Phobos (driver/linker.cpp). ground is -betterC and links sqlite3,
curl and git2 (ground dub.json).codesign -s - runs on the machine that lands
it (ground source/comet.d).TODO: move section to the root agent ADR
"to get ground setup for the ROOT agent"
TODO: talk about comet ui needs to be owned by Web "which is for all of this to be visible in the existing Element in the ui, remvoing the coment crosshatches"
"which is for A2A agents to receive a coment first, or be known that they run under ground before they do A2A shut"
ready in server/claude.go, which checks the Claude Code
binary and the plan token. A comet held for the harness is checked there.TODO: UI CONCERN "How the node holds private controls, It should be somewhat doable in the UI"
"Well, each user has different preferences, so in reality you build ground per user per their project"
exec ground on PATH: one binary that path-matches every
project. Claude Code reads
hooks from a repository's own .claude settings as well as the user's; how
both combine when both name ground is not verified."Yes, USER uses ground, but they dont think about it because it just lands via comet"
ground <version> (ground source/db.d). That is how the node knows which
ground a session runs, and so which comet landed."i see, those stubs, why not send to s3 in a manner that is documented"
aws s3 cp --recursive. The
stubs go there as a build input.sdk/MacOSX26.1.sdk and sdk/aarch64-darwin/libgit2.dylib in
the bootstrap bucket (the deploy repository's infra/macos-link-stubs.tf). The reconciler
syncs them to the node's ~/.qntx/darwin-stubs (infra/bootstrap/apply.sh),
「[Opus 5.5] where server/comet linked a whole ground against them. A sand imports no」
「[Opus 5.5] symbol and links against nothing (server/comet sandLinked).」"another thing i want is that rituals run on the box from now on, not locally on my machine per se."
claude -w <tree> --bg --permission-mode dontAsk, ground bind ties
the agent to the performance and claude stop ends it (ground
source/ritual/run.d, drive.d). The deploy ritual runs make ats, dispatches
a workflow, writes an SSM parameter and reads crowbar --show-qntx-versions.-p (run.go), not --bg. The box's role
writes one plugin's SSM parameters and no other./comet/{owner}/{repo}/{platform}: POST builds, GET serves with its digest,
?digest and HEAD answer the digest alone (server/comet).
The Darwin build on the box, end to end, with the stubs from S3: grove's aarch64-darwin comet, built on q, landed on the operator's machine.
Landing: sky pulls the digest every five seconds and renames a checked comet over the one there (ground source/sky.d).
A push to a project's default branch, or to ground's main, rebuilds the comets it moves.
Comet on am ground, and the Comet stratum real.
「[Opus 5.5] A comet is the sand alone: POST /comet/{owner}/{repo}/{platform} builds」
「[Opus 5.5] ground main's make sand, kept by the engine ABI it wrote; GET」
「[Opus 5.5] /comet/{owner}/{repo}/{platform}/{abi} serves it to the ground of that ABI,」
「[Opus 5.5] which loads it (ground source/sandload.d).」
ground for the Node Agent: its settings.json runs it, and no turn is said to
the agent until it stands. On q its rows name ground comet a1ac2c0 agent:root and reached the node.
Under -p Claude Code waits for an asyncRewake hook to end: q's agent turn
held on its sky's day-long timeout. An agent's sky is spawned apart.
The sand on the node, configured by a person: a POST names the machine repository, and its controls/ fold in beside ground's own and the project's. grove's comet for k's machine names its three revs in its rows and k's node in its sand.
aarch64-linux from the box: ld.lld links against that platform's libraries from the binary cache at ground's pin. q's build of grove ran under qemu-aarch64 on k as grove's ground.
A comet lands from its machine's node, on the box: grove's comet for the box's own machine names q, and the Node Agent's sky landed it from q in its home, digest 77ef85de.