User / operator board
Installation, local operation, identity and rights usage, BTDU ingestion/recovery, passports, market workflows, documentation and practical troubleshooting.
Ask, build, test, challenge and share.
The board is for people building, integrating, evaluating, operating or using ENTITY. GitHub Discussions is the conversation layer; this page is the routing and evidence guide.
Installation, local operation, identity and rights usage, BTDU ingestion/recovery, passports, market workflows, documentation and practical troubleshooting.
SDK/CLI/API integration, protocol interpretation, conformance, BTDU/ADAM/NIKI boundaries, standards mappings, market/economic semantics, recovery, adapters and architecture proposals.
Questions with a concrete answer path: setup, APIs, behavior, conformance, recovery, markets or subsystem boundaries.
Open Q&A →Evaluation, operating experience, architecture discussion, onboarding feedback and observations that are not yet a tracked defect or proposal.
Start general discussion →Proposed runtime, protocol, integration, documentation or community changes. Ideas remain proposals until implemented, reviewed and qualified.
Propose an idea →Integrations, apps, independent implementations, reproductions, benchmarks, tooling, standards work and deployment experiments.
Share work →Maintainer-posted releases, qualification milestones and project updates. Community members can reply.
Read announcements →Use polls for bounded community preference questions, not for deciding protocol truth, security findings or qualification status.
Open forum →Installation, environment, tutorials, recipes, CLI and first integration.
Identity, delegation, revocation, permissions, rights constraints, passports and custody boundaries.
Governed information, exact reconstruction, deterministic state/replay and bounded reasoning.
Claims, attestations, provenance, Protocol 1.0, clean-room implementations, standards and external reproduction.
Rights instruments, venues, orders/RFQs/auctions, clearing, settlement evidence, entitlements, usage and participation.
Provider-independent exports, cold recovery, partition behavior, offline state and continuity testing.
Questions, ideas, design conversation, evaluations and user/developer experience.
GitHub Discussions →Reproducible defects, concrete ambiguities, documentation errors, qualification failures or bounded work items.
GitHub Issues →A concrete proposed change with a reviewable diff and test/evidence path.
Pull requests →These states are intentionally separate. A local PASS is not independent validation. An upstream merge is not payment. Provenance is not ownership. A Discussion consensus is not a protocol change.
Critique implementations, claims and evidence. Reproducible failures, counterexamples and incompatible interpretations are useful contributions. Respect privacy and security boundaries and distinguish implemented, tested, qualified, experimental and proposed work.