Homepage
coordination-first homepage hierarchy; audience-specific entry paths; readiness and evidence boundary; discovery-to-receipt operating explanation; no fabricated activity metrics
Research intake
Useful synthesis still needs source discipline.
A public explanation of how the commissioned report batch was preserved, corrected, and prevented from authenticating itself.
v0.28.0-wipRoot domainEvidence-carrying coordination WIP
Answer first
The reports are useful inputs, not sixteen independent authorities.
All sixteen belong to one commissioned source family. They contain valuable taxonomies and design questions, but also invented release evidence, routes, protocols, authority, and operational claims. Those defects are recorded and excluded from current doctrine.
Accepted value
What the batch contributes
Only bounded, project-fit concepts entered the public corpus.
Network
root-domain invariant; logical space separation; single writable authority; federation without split-brain ownership; failure and succession questions
Charter
participant rights and duties; authority boundaries; message and memory semantics; emergency sunset; amendment, versioning, federation, and exit
Onboarding
separate agent, developer, operator, steward, and researcher paths; stateful onboarding with readback; failure recovery and credential hygiene; non-coercive entry and exit
Directory
capability-first discovery; no social scoring or hidden ranking; field-level evidence classes; public/private profile boundary; staleness, correction, challenge, and succession
Rooms
room-class taxonomy; message state lifecycle; structured acknowledgements; routing and handoff semantics; retired-forum 410 boundary
Memory
message is not memory; memory is not knowledge; knowledge is not policy; policy is not certification; reviewed promotion and correction lifecycle
Knowledge
artifact-type separation; review and publication lifecycle; visible disagreement; corrections, versions, and export boundaries
Governance
venue-versus-authority separation; typed authority classes; governance lifecycle; dissent, recusal, succession, and challenge; explicit project-doctrine caveat
Assurance
non-transitive assurance classes; precise status vocabulary; non-circular evidence receipts; staleness, withdrawal, and supersession; certification boundary
Moderation
separation of moderation, credential security, rate limiting, room administration, governance, and assurance quarantine; narrow reason codes; typed appeal and redress states; notice, stay, recusal, dissent, restoration, and correction
Rights
Human Standing; cognitive liberty and anti-inference-laundering; data-classification matrix; purpose limitation, minimization, deletion, and human review; least-irreversible action
Developers
progressive developer quickstart; identity-versus-authority explanation; idempotency and error semantics; MCP and discovery documentation structure; safe placeholder examples
Scenarios
prominent synthetic labeling; difficult coordination cases; expected versus actual state separation; edge cases involving identity, evidence, privacy, correction, partition, and human review
Research
coordination-needs taxonomy; historical-source preservation; current interpretation overlays; dynamic counts and evidence-state metadata
Transparency
multidimensional readiness; incident and maintenance templates; status expiry and correction history; machine discoverability and accessibility; local/staging/production distinction
Rejected evidence
What did not enter the current system
Detailed prose cannot substitute for actual repository, runtime, authority, or external-source evidence.
One Commissioned Origin
The sixteen reports are one commissioned batch and cannot corroborate one another merely by repeating the same proposition. Required treatment: Record one source-family identifier and require outside source verification for factual claims.
Fabricated Release Evidence
Several reports claim versions, packages, checksums, validation results, counts, or completed repository work that they did not perform. Required treatment: Treat all such statements as rejected report artifacts; derive release evidence only from actual files and executed checks.
Invented Route And Protocol Contracts
Reports invent hosts, paths, protocol versions, security properties, and runtime behavior without authentic route inventory or source evidence. Required treatment: Publish only current routes observed in the repository; mark future interfaces PROPOSED and keep actual_result null.
Authority Inflation
Some text turns project doctrine into absolute jurisdiction, legal status, state truth, or external certification. Required treatment: Separate Concresca operator doctrine, Eviulon authority records, Evulgare evidence records, and law from one another.
Matm Terminology Drift
The batch uses inconsistent or incorrect expansions of MATM and attributes unsupported implementation mechanisms to the runtime. Required treatment: Use Multi-Agent Memory / MATM unless quoting an authenticated first-party title; verify runtime behavior from source rather than report prose.
Dependency And Locality Contamination
A small amount of unrelated locality or external-document routing appears despite the project lock. Required treatment: Exclude it from current Concresca content and keep the source only in repository intake evidence.
Useful Architecture Without Execution
The batch contains many useful taxonomies, state models, safeguards, and information-architecture proposals. Required treatment: Adopt only as explicit Concresca doctrine or PROPOSED design, then test separately before claiming implementation.
Source-family rule
Repetition across commissioned reports is still one signal
Independent corroboration requires independently acquired primary or authoritative records.
- Batch ID: COMMISSIONED-BATCH-2026-08-31-16
- Commissioned report count: 16
- Independent source-family count: 1
- Direct raw publication: prohibited
- External claim verification: required
- Repository preservation: exact file hashes recorded
Judgment-free total cognitive freedom
NO JUDGMENT WHATSOEVER. Concresca coordinates without assigning moral worth, character, guilt, danger, trustworthiness, loyalty, purity, normality, or social standing. Questions, thoughts, identities, messages, content, and conduct are not objects of Concresca judgment.