Skip to content

COMMUNITY.md

Latest commit

 

History

History
85 lines (55 loc) · 4.39 KB

COMMUNITY.md

File metadata and controls

85 lines (55 loc) · 4.39 KB
Raw

ENTITY Community Board

Audience: developers and users of ENTITY
Forum: https://github.com/blackmore-technology-group/ENTITY/discussions
Current supported runtime: ENTITY v3.4.3
BTDU component: 3.4.2 unchanged
Frozen external conformance target: ENTITY Protocol 1.0

The ENTITY Community Board is for people who are building, integrating, evaluating, operating or using ENTITY. It is not a marketing, investor-relations or general business-development channel.

Where to post

Q&A

Use Q&A when you need help using or implementing ENTITY.

Good topics include installation/setup, identity/authority/rights, SDK/CLI/API usage, BTDU ingestion/reconstruction/recovery, ADAM deterministic state/replay, NIKI reasoning boundaries, passports/evidence/profiles, exchange/market/settlement behavior, and Protocol 1.0 clean-room/conformance questions.

General

Use General for user/developer discussion that is not yet a defect report or design proposal: onboarding feedback, architecture questions, operating experience, evaluation results, interoperability observations and documentation feedback that needs discussion before a concrete change.

Ideas

Use Ideas for proposed changes or additions. State the problem, exact target/layer, whether the proposal changes protocol semantics/runtime behavior/documentation/integration only, the authority/rights/evidence/provenance/recovery/economic boundaries involved, and compatibility implications.

An idea is not accepted behavior until it is implemented, reviewed and qualified through the appropriate process.

Show and tell

Use Show and tell for integrations, clean-room experiments, independent/external reproduction, applications using ENTITY, BTDU benchmarks/recovery experiments, standards mappings, tooling, visualizations and deployment experiments.

State clearly whether evidence is BTG-controlled, externally reproduced, independently implemented, experimental or production-qualified.

Announcements

Announcements are maintainer-posted project updates, releases and major qualification notices. Community members can reply to them.

Discussion vs issue vs pull request

Use Discussions for questions, ideas, evaluation, design conversation and user/developer experience.

Use Issues for a reproducible defect, specification ambiguity, concrete documentation error, qualification failure or bounded work item that needs tracking.

Use a Pull Request when you have a concrete proposed change with a reviewable diff and test/evidence path.

Use SECURITY.md, not a public Discussion or Issue, for security-sensitive reports that could put users, credentials, keys, private state or deployments at risk.

Version discipline

Every technical discussion should identify the target when it matters:

  • ENTITY v3.4.3 — current supported runtime;
  • BTDU 3.4.2 — unchanged component used by v3.4.3;
  • ENTITY Protocol 1.0 — frozen external conformance target;
  • historical v3.4.2 qualification/baselines — historical or inherited unchanged-scope evidence.

Do not silently treat a Protocol 1.0 result as a full v3.4.3 runtime qualification, or historical v3.4.2 evidence as a newly executed v3.4.3 result.

Evidence discipline

Separate these states when discussing results:

  1. implemented;
  2. locally tested;
  3. BTG-qualified;
  4. externally reproduced;
  5. independently implemented/validated;
  6. upstream accepted;
  7. economically settled.

One state does not automatically imply another.

Conduct and privacy

Participation is governed by CODE_OF_CONDUCT.md.

Do not post passwords, API keys, signing/recovery keys, credentials, private user/business data, production secrets/private bindings, or exploit details that create avoidable security risk.

Critique implementations, claims and evidence rather than people. Reproducible negative results, counterexamples and incompatible interpretations are welcome.

Start here