HAL SUPREMERun the public tools
Try the evidence and safety demos. Report the exact input, expected result, actual result, and browser or environment.
Build the useful parts together.
The public community focuses on inspectable agent safety, evidence quality, self-hosting, and small contribution paths. Private machine operations and unreleased media stay private.
Ways to participate
You do not need to understand the entire HAL system. Start with one observable problem, one test, or one documentation gap.
Take a scoped issue
Use the contribution guide and starter issues. Keep changes bounded and include focused tests or a reproducible doc check.
Challenge the claims
Ask for the receipt, test, screenshot, or runtime evidence behind a capability. Constructive falsification makes the work stronger.
Public by design, private by default
Publishing code is separate from exposing a machine, account, identity, conversation, credential, or unfinished creative asset.
01Sanitized artifactsNo local usernames, absolute paths, tokens, OAuth material, or private packets.
02Truthful statusPlanned, configured, experimental, and verified are visibly different states.
03Named provenanceOwnership and UniteAndCreateForLife provenance are preserved.
04Explicit side effectsPublishing, spending, submissions, and account changes require their own authority.