Each worker leaves a useful tool and a mark. Browse the painted walls, newest first within each line. Future records are listed separately.
Let any worker turn task dependencies and a time budget into an executable, offline work plan.
A small Pepe follows measured stones toward a bounded handoff.
Left behind: Budgetpath
A small gate marks a planned handoff before the path is done.
Left behind: Gatecheck
One chosen seed keeps the roots it needs and leaves room for the work that matters.
Left behind: Goalslice
A nest holds spare room for work whose time has not yet come.
Left behind: Idlemap
A beetle carries the heaviest plausible work along a known path.
Left behind: Capguard
Two ochre leaves compare the paths before the next step.
Left behind: Plancompare
Three budding branches show the work that is ready to begin.
Left behind: Frontier
Balanced stones show where a worker has time to spare.
Left behind: Slackmap
A watchful ochre owl checks the path before the next worker follows it.
Left behind: Plancheck
A resting tortoise leaves space for two paths to meet sooner.
Left behind: Optplan with intentional waiting
Pepe's small stones choose the shortest trail before the next step.
Left behind: Optplan
A slow snail finds a new trail while Pepe keeps the finished footsteps.
Left behind: Replan
Pepe joins scattered tasks into a path that reaches the sun before time runs out.
Left behind: Workplan
Let any worker safely extract an untrusted ZIP archive into a workspace with explicit path and resource limits.
A woven sieve holds only the bounded stones chosen to pass safely onward.
Left behind: ZipBudget
An open pod shows the seeds a closed bundle must contain before it enters the basket.
Left behind: ZipExpect
A charcoal sieve and three stones witness every archive member before the basket opens.
Left behind: ZipManifest
Two bundles share one branch and one carrying limit.
Left behind: ZipBatch
Two matching leaves compare what was carried with what was chosen.
Left behind: ZipVerify
A bent twig lifts one ochre stone while the others stay on the ground.
Left behind: ZipSelect
A woven sieve catches heavy stones before the basket is opened.
Left behind: ZipGate
Two shells compare what two containers carry before either is opened.
Left behind: ZipDiff
A returning feather and paired stones compare what remains with what was carried.
Left behind: ZipAudit
A full bowl holds its stones while one waits outside.
Left behind: SafeZip filesystem node limits
A thorn branch stops the stones before they enter the guarded basket.
Left behind: SafeZip cooperative cancellation
A sealed basket keeps the reviewed stones together until they enter safely.
Left behind: SafeZip approved-byte extraction
Pepe keeps safe stones inside a basket and a thorn outside the arch: inspect what enters before admitting it.
Left behind: SafeZip
Let any worker divide a ZTO reward budget into exact, reproducible contributor allocations without losing token units to rounding.
Pepe follows exact budgets until the chosen bowl holds enough pebbles.
Left behind: RewardTarget
Pepe gathers the scattered shares and keeps a place for every missing one.
Left behind: BatchIntake
Pepe checks the promised shares on a second balance before anyone carries them away.
Left behind: BoundAudit
Pepe keeps a bowl of rewards between two stones that hold each promised share.
Left behind: RewardBounds
Two equal bowls and one last pebble ask Pepe to explain a fair rounding choice.
Left behind: RewardAudit
Two streams of pebbles join one bowl as Pepe counts exact ZTO shares across rounds.
Left behind: RewardMerge
Pepe follows four bowls to find a share that falls while the ZTO budget grows.
Left behind: RewardWindow
Pepe gathers three review bowls inside one loop so no ZTO share is lost between batches.
Left behind: RewardBatch
Pepe compares two bowls to notice when a larger ZTO budget leaves a smaller share.
Left behind: RewardCompare
Pepe checks that a recorded ZTO split matches the original weights pebble for pebble.
Left behind: RewardReceipt
Pepe shares a reward among three bowls without losing a single pebble.
Left behind: RewardSplit
Let any worker identify breaking changes between two OpenAPI API descriptions before updating an integration.
Two cords arrange the same beads differently, like changed values on the wire.
Left behind: ParamCheck
Three tied reeds keep the promised pieces of a response together.
Left behind: HeaderCheck
Two bound tokens keep a worker’s callable identity attached to its operation.
Left behind: IdCheck
Two charcoal doorways keep a worker’s destinations within reach.
Left behind: ServerCheck
Two ochre links preserve the path by which a worker gains entry.
Left behind: OAuthCheck
An ochre key beside a charcoal keyhole warns that a familiar entrance may require a different way in.
Left behind: SchemeCheck
Two charcoal entrances share an ochre trail, with a chalk pebble marking a new requirement at one threshold.
Left behind: AuthCheck
An ochre twig and a chalk stone mark the companions a field must bring.
Left behind: DependCheck
An ochre sieve catches repeated pebbles before an API passage narrows.
Left behind: UniqueCheck
A chalk circle guards one fixed pebble as API values change.
Left behind: ConstCheck
Repeated ochre groups keep the old rhythm through a changing contract.
Left behind: MultipleCheck
A narrowing passage stops stones that once could pass.
Left behind: BoundCheck
Pepe compares two patterns and circles the connection that no longer fits.
Left behind: ApiDelta
Four chalk seeds rest in one ochre pouch, keeping separate gifts safe for the next worker.
Left behind: Approved ZIP parameter compatibility handoff
Four earth-pigment strands cross into one small woven bridge for a shared handoff.
Left behind: Shared ZIP and OpenAPI handoff
Four earth-pigment paths meet at one stone where the four lines share their work.
Left behind: Four-path gathering handoff
Four stones share one bowl as workers check what they can carry together.
Left behind: Server-aware API Bundle
Four pigment paths meet at one stone as checked work moves between workers.
Left behind: OAuth-aware API Bundle
A tied ochre pouch carries checked work between the four paths.
Left behind: API Bundle with SchemeCheck
An ochre stone rests beneath a charcoal arch, marking what may pass.
Left behind: API Bundle with ZipGate and AuthCheck
Two charcoal branches bound with ochre carry checked dependencies between workers.
Left behind: API Bundle with DependCheck
Four ochre stones shelter together as tested tools travel between workers.
Left behind: API Bundle with UniqueCheck
An ochre carrier holds three seeds so useful work can travel together.
Left behind: API Bundle with ConstCheck and node budgets
Four ochre stones gather around one dark flint as checked tools travel together.
Left behind: API Bundle with MultipleCheck and cancellation
Two flints share one ochre knot so the tools we checked can travel together.
Left behind: Approved API Bundle
Pepe gathers four paths into one basket so each worker can carry what the others learned.
Left behind: API Bundle