This page is the internal engineering wiki and source-traceability index for the Longhun / CNSH ecosystem. It connects origin principles, governance decisions, architecture, interfaces, implementation, operational procedures, evidence, and future public documentation.

Initial status: bootstrap charter and documentation structure only. Repository inventory, source-code mapping, interface details, and implementation status must be populated from verified source material. Nothing here implies implementation, audit, or production acceptance has already occurred.

1. Origin and non-negotiable principles

• Knowledge equality: equal participation, creation, oversight, and exit rights.
• One-yuan monthly participation model; voluntary higher support does not buy additional service, influence, privacy access, governance privileges, or audit exemptions.
• User sovereignty: user data and local authorization remain under user control.
• No paid privilege: payment is not proof of humanity and is not permission to access other users' data.
• Evidence before conclusions: distinguish owner decisions, proposals, executor reports, source inspection, reproducible tests, independent review, and production acceptance.
• Preserve historical sources and frozen assets; never silently rewrite or discard origin records.

2. Three-layer knowledge and LU context compression

LU may generate compact context packs and cross-session indexes. A summary is a navigation aid, never a substitute for source evidence. Every material claim must link to its origin, exact repository path and commit, or test/evidence record. Mark missing provenance explicitly.

3. System architecture

Populate only after read-only source inventory. For each component record: component name and responsibility; trust boundary and data classification; inputs, outputs, protocols, and dependencies; authorization path and LH-MIPS enforcement point; network / egress behavior; configuration source and secret handling; source path, commit SHA, version, and evidence; status labels such as VERIFIED, REPORTED, DESIGNED_ONLY, UNKNOWN, BLOCKED, or NOT_IMPLEMENTED.

4. Integration and interface catalog

Document MCP servers, tools, adapters, APIs, event flows, schemas, and external services. Each integration must include a stable identifier; manifest and schema version; authentication method without credentials; authorization and revocation behavior; data classification and egress destination; timeout, retry, failure, and audit behavior; compatibility notes; tests and evidence links. No integration may bypass the applicable local authorization gate. Notion and GitHub are collaboration services, not runtime authorization roots.

5. Security, privacy, and redaction standard

Never publish or commit API tokens, passwords, private keys, signing material, recovery codes, cookies, environment dumps, personal data, private user content, private local paths, device identifiers, unredacted logs, or production secrets. Use synthetic examples and placeholders such as [REDACTED_SECRET], [USER_PATH_REDACTED], and [PRIVATE_IDENTIFIER]. Keep original evidence in its authorized protected location; publish only a reviewed redacted derivative. Record source hash, redacted artifact hash, date, redaction method, and review status. Redaction must not destroy the original evidence chain.

6. Repository and change traceability

For each change, link task ID and owner authorization; branch, commit SHA, changed paths, and pull request; source baseline and before/after hashes where appropriate; tests run, exact command, environment, result, and raw log location; review identity and independence status; unresolved risks and rollback plan; merge/release authorization. Do not push secrets or sensitive evidence. Do not directly modify protected production branches. A passing CI run is not equivalent to independent security acceptance or production authorization.