Show HN: CapOS – A responsibility-gated OS stack with signed process execution
4 comments
·May 2, 2025dwb
I’m interested in capability systems, have wondered about a project like this before, and you may well be onto something, but the self-important (and, as far as I got, insubstantial) philosophy is extremely off-putting.
cyberax
> X^∞ - Postmoral and Emotionless: Mathematical Foundations of Ethical Governance as a Self-Reinforcing System > The Auctor
Ah, perhaps they might be interested in publishing my monograph: "Transgressing the Boundaries: Towards a Transformative Hermeneutics of Quantum Gravity"?
Der_Auctor
You're right to invoke Sokal – he exposed what happens when structure is absent, but language remains. X^∞ does the opposite: structure without flourish. The Cap system isn't meant to sound good – it’s designed to enforce responsibility without ideology, emotion, or rank. We’re not postmodern. We’re postmoral.
LargoLasskhyfv
Where is the bootable image? I seem to smell a faint whiff of Xanadu.
We’ve built a functional prototype for an operating system layer that rejects the classic trust model.
Every process, network access, and system action is explicitly scope-bound to a signed capability token (CapToken) – backed by a cryptographic wallet and domain-specific responsibility structure.
Key Components: CapToken authentication for all system actions
CapAuditDaemon (feedback, incidents, signed system state)
Feedback replaces control – the system acts on effect, not permission
CapNFTs as soulbound responsibility certificates
VPN routing via chain-verified nodes (CapVPNRegistry.sol)
Whitebook & mathematical formalization published on Zenodo
No ACLs, no root, no anonymous processes. Only signed, trackable responsibility. Period.
GitHub: https://github.com/Xtothepowerofinfinity Docs/Whitebook: https://zenodo.org/communities/xtothepowerofinfinity
Feedback kills control. Power demands responsibility.