cyberia/projects.md

projects

the projects lens of org: work that closes. a project is a task with sub-tasks (dev § the objects); it has an owner, a status and a page, and when every sub-task is done it is over — unlike a product, which is kept alive, and unlike the chronicle, which is infrastructure. a project's domain is an attribute of the project, as a product's is of the product; the registry of every domain the state holds is cybernode's, at domains.cybernode.ai.

this folder is the registry: one file per project, its passport — what it is, its domain, its repository, its stage, what it serves. a project that needs more than a passport keeps the rest in its own repository, never in a folder here.

a project is finite: it has a delivery, a date and a declaration — the page its link opens (the owner, 2026-11-16). what is kept alive and measured by revenue and capacity is a product and lives on products; a site is a product's door, never a project's. the order of this table is the priority: the first row is worked first. the owner moves a row up or down here, by hand or from the cockpit's projects tab, and every move is a commit — the history of priorities is the history of this file. there are no proposals any more, only projects (the owner, 2026-11-16): every repository keeps its projects in projects/, one page each, with status: in the front matter — proposed (a decision still open), accepted (decided, being delivered), executed or done (delivered, the date beside it), rejected or superseded (history). the page is the project's declaration. soft3's proposals/ became projects/ that day; cybernode was the first.

how the table fills — from the bottom

the apparatus collects projects from the bottom: apparatus/scripts/projects_collect.py (run by the cockpit's collector every 15 minutes) reads projects/*.md of every repository under cyberia-to — on its default branch and on its release line (release/phase1, where soft3 integrates) — and every page has a row here, whatever its status: this is a management system, everything is seen (the owner, 2026-11-16). the row's stage is the page's status — draft, proposed, accepted, done (executed, implemented, delivered), rejected, superseded. the product column says which product the project serves: the collector fills it from the page's repository, the owner corrects it here, and the cockpit counts projects per product from it. the part of column makes the projects a tree, as the products are (the owner, 2026-11-18): it names the project this one is part of, set by the owner from the project's page in the cockpit (a signed command the executor writes here), or — for a top project. every project has its page in the cockpit (/project/): the generic page shows what this table and the passport say; a passport may name a custom view in its front matter (view: launch — the launch of spacepussy draws its live chain), registered in apparatus cockpit/project.js. a page without a row is appended at the bottom — the lowest priority until the owner drags it up — with the page as its declaration, its first sentence as the delivery and its date: as the date; a row whose page's status changed takes the new stage. the collector never reorders and never deletes: priority and removal are the owner's hand. each run that changes the table is one commit on cyberia main.

project product part of waits for delivery date stage
launch spacepussy $PUSSY — — the public pussy chain live with proofs, revertible, on the explorer by readiness (red date 2026-11-05 passed) doing
launch century index cx button — the index published every day at cx.cyberia.my, and the first lease priced in CX signed — doing
button my cyberia — midao registration a plot on cyberia.my sold with the button: paid by bank or by crypto, its documents signed and registered, the right recorded — accepted
design state economics soft3 launch spacepussy — two products, three channels, four rules, one curve. — proposed
complete rewards soft3 launch spacepussy — On the public pussy chain a stake on a link earns and loses by the whole law of rewards, and the loop closes: what an epoch learns changes what the next epoch weighs. — proposed
the hybrid economy soft3 complete rewards — Pussy's chain mints by the law of adaptive hybrid consensus economics: the budget of an epoch is a security floor derived from what an attack costs plus the fee — proposed
activation soft3 complete rewards — A staked cyberlink on pussy's chain says two things the truth serum can score — which side its author stands on, and what its author expects of the crowd — in a — proposed
the truth market cybergraph complete rewards — On pussy's chain at genesis every staked cyberlink carries the whole truth mechanism of rewards §5: a side, a stake and a prediction of the crowd; a market on t — proposed
prove every block soft3 launch spacepussy — the property, fixed by the owner on 2026-10-17 as a base property of the system, cross-cutting and necessary: — proposed
present proves the past soft3 launch spacepussy — parano1d is a production proof-native chain: 393 kLOC, 20 crates, mainnet live since 2026-08-21, every block carrying a recursive validity proof, PoW ordering o — proposed
repair zheng into one proof joy launch spacepussy — hemera note (2026-10-16): the hash row below is decided — hemera 0.4 (hemera#15: x⁷ in every round, 6 + 6 + 48 rounds, Poseidon2 reference matrices, 32-byte dig — proposed
define the consensus clock soft3 launch spacepussy — soft3 has proofs (zheng), a state organ (bbg), a graph (cybergraph), a compiler (trident), a mining spec (fold-mining) — and no working blockchain. — proposed
networks as repositories soft3 launch spacepussy — the owner, 2026-10-17: every network has a configuration — a set of contracts (plumb), the genesis distribution, the starting parameters, the starting graph: a — proposed
name the assumptions soft3 launch spacepussy — The stack keeps one list of everything it assumes and cannot prove. — proposed
the combine apparatus — — Every pull request of the organisation passes the inspection of the whole infrastructure before the owner sees it: whether it serves a project and a product, wh — doing
write the chronicle cyberia — — The whole history of the project, from every source, read and told as one chronology: interesting, understandable and connected, with the price of BOOT running — accepted
fathership cyberia — — — — doing
command from the apparatus apparatus fathership — The owner, or a person the owner names, writes a command in the apparatus and signs it with a web3 wallet. — doing
ship the first kadek release cyb — — kadek v0.1.0: the first tagged release, carrying the foundation the closure order names phases 1 and 2 — clocks, configuration, admission, provenance, presentat — accepted
sell oxytocin cyberia — — the one-threshold space in Sayan, Ubud, sold — everything for the sale is there, it has to sell — doing
fill the civics of cyberia cyberia — — the six slots of cyberculture filled at cyberia: cosmology, calendar, ritual, canon (the library of concepts), etiquette, aesthetics — proposed
launch bostrom $BOOT — launch spacepussy bostrom reborn as a public soft3 chain from its burial snapshot — after spacepussy launches and is debugged after launch spacepussy open
host events cyberia — — — — paused
research genome protocol cyberia — — a page of knowledge — research
research migration market cyberia — — a page of knowledge — research
research tech tree cyberia — — a page of knowledge — research
research noid market cyberia — — a page of knowledge — research
research smart capital cyberia — — a page of knowledge — research
carve cybernode out of soft3 cybernode — — the node carved out of soft3, its own repository 2026-10-27 done
prove finality by views cybernode — — finality as evidence, not declaration: the quorum certificate without the — draft
align kadek with soft3 cyb — — final audit. — proposed
build private recovery index neural — — make opening or restoring a private wallet depend on the wallet result requested, — draft
give each component one page soft3 — — every component of the stack answers at one canonical address on — draft
merge sync and tade soft3 — — Superseded in part: the sync repo has since merged into foculus — the structural-sync substrate and the fork-choice that completes its merge are now one crate. 2026-06-07 done
metabolic oracle in core soft3 — — cyberia's architecture carried a mechanism that answers one question for a whole network: is it alive? It was written for cyberia's 147 agents. — proposed
cut the network into planes soft3 — — builds on cybergraph + sync + tade (2026-06, implemented), which merged the sync repo into foculus to kill two owners of one mechanism, and on component boundar — proposed
freeze the privacy design soft3 — — hemera note (2026-10-16): the hemera#15 decision this page waits for is taken — hemera 0.4 (x⁷ in every round, 6 + 6 + 48 rounds, 32-byte digest kept) is the fr — proposed
root the civilization soft3 — — soft3.org sells a machine: collective, private, provable computing, thirty features, seven verbs. — proposed
exchange only in tade soft3 — — builds on cybergraph + sync + tade (implemented 2026-06), which made tade the wire substrate under radio and foculus. — proposed
program the rights soft3 — — three inheritances, one language. — proposed
research cyber sheep cyberia — — a page of knowledge — research
give vault its own home cy — — Vault is now an independent component in — superseded
add dynamic noun memory joy — — This project extends the native Zheng execution relation toward computed — draft
try tagged symbolic relation joy — — This project defines execution::tagged, an opt-in circuit kernel. — draft
the globe my cyberia — — the owner, 2026-11-17: the home of cyberia.my becomes a globe, and the map is the primary way to use the site. 2026-11-17 done
serve our own imagery my cyberia — — the owner, 2026-11-18: "maybe we think about a resource for serving satellite imagery?" — this page is that thought, for a decision. — proposed
prove the protocols soft3 — — A proof system is three statements, and each has a different kind of proof: — draft
define the receipt soft3 — — A proof is evidence. — proposed
merge agents into one fleet apparatus — — The owner, 2026-11-18: merge machines, services and agents into one entity. — proposed
contractions as triggers apparatus — — The owner, 2026-11-18: contractions now merge into processes, but with thought. 2026-11-18 done
midao registration $CAP | button | — | the legal body of $CAP formed in the Marshall Islands: a certificate, an operating agreement on its on-chain governance, and an account the button pays into — doing
base cartography my button — on cyberia.my a person draws points, lines, plots and buildings on their own layers over the one globe, verifies a boundary standing on it, and publishes by one signature — accepted
the calendar apparatus — — the owner, 2026-11-21: "a separate screen of the organisation's calendar — where events land in the future, and where everyone sees his priorities for now. — accepted
the land market my — — the owner, 2026-11-20: an admin interface and a funnel for the owners who want to place their plots on the map for sale or lease. — proposed
the process engine apparatus — — the owner, 2026-11-21: "processes can be expressed as schemes, looped ones too. — proposed

research packs — a project whose output is a page of knowledge — sit in the same table and the same folder since 2026-10-23 (they were research/). moved to products on 2026-11-16 because they are kept alive, not delivered: cyber valley, the land console (my cyberia), cve, cyberstates, the meme state, etherland, cyberia capital, rockets. the source of everything is github.com/cyberia-to.

Folder

Homonyms

projects
projects
cyber/projects
soft3/tru/projects
projects
soft3/zheng/projects
projects
cybics/crystal/projects
cyber project is structured around ~20 public projects and ~10 more internal cyb and cyber cyber: cyber v4 cyber v5 launch cyber growth: cybernode: cyb: main board which is decomposed primary to cyb components cyb/sigma cyb/time cyb/brain cyb/sense cyb desktop aos apps for cyb cyb/portal teleport…
cyberia/cyberia-my/projects
projects
soft3/cybergraph/projects
projects
soft3/mudra/projects
design projects draft projects define candidate constructions and experiments. accepted requirements live in the canonical module and composition contracts. | project | status | question | |---|---|---| | [private recovery index](/soft3/mudra/projects/private-recovery-index) | draft |…
soft3/foculus/projects
projects

Graph