GEWU/docs/reviews/ARCHITECTURE_REFERENCE_REVIEW.md

Architecture and protocol reference review

12 October 2026. Scope: current local documents supplied by the owner, compared with GEWU PRD 0.7 and GOAL. This is a document review, not a live acceptance audit of AAA, Jev or Sonification.

Finding

Borrow explicit contracts, clear module ownership, durable evidence and careful frontend lifecycle management. GEWU's product boundary requires a smaller runtime than AAA and a stronger acceptance boundary than an advisory agent router. Reference rules are evaluated individually; their status labels and imperative wording do not make them GEWU instructions.

Reference inventory and disposition

Paths below identify the local source material under D:/01_GIT/. They are provenance labels, not required cross-repository dependencies. Portable GEWU protocols live in this repository and do not require those files at runtime.

Reference	Keep or adapt	Do not carry into GEWU
AAA/docs/development/practices/SCAFFOLDING_AND_DEVELOPMENT_RULES.md	Explicit tiers, bounded schemas, central composition/lifecycle, isolated tests and documented gates.	Cognitive ProcessingModule/daemon scaffolding; blanket cascade-delete advice; generic BackgroundTasks for critical acceptance; AAA-specific skill mandates.
AAA/docs/development/practices/BACKEND_BEST_PRACTICES.md	Short transactions, bounded concurrency, upload/SSRF defenses, structured safe errors, typed new code and private diagnostics.	Copying thread-local connection decorators into async work; per-conversation locking as a substitute for a global canonical writer; assuming threads isolate hostile parsers.
AAA/docs/development/practices/FRONTEND_BEST_PRACTICES.md	URL state, request/subscription cleanup, demand-driven work and scoped source typography.	Blanket memoization and custom comparison rules; a telemetry pub-sub system before measured need; obsolete clipboard fallback as a universal requirement.
AAA/docs/development/practices/FRONTEND_DESIGN_PRINCIPLES.md	Consistent shared components, readable list/detail navigation, source sanitization and entity-bound async lifetimes.	Terminal-only typography, tiny 8–10 px labels, hidden chrome rules overriding accessibility, or chat/research authoring workflows.
AAA/docs/development/proposals/locked_page_artwork.md	A clear artistic premise tied to specific behavior.	The artwork itself: private-content teasers, text dimming, compressed ghosts and animated accumulation do not serve GEWU reading.
AAA/docs/architecture/ARCHITECTURE.md	Lifespan-owned composition root, route/use-case/storage separation and explicit data flow.	Fifteen-stage reasoning pipeline, dream metabolism, internal model orchestration or raw conversation storage as the domain.
AAA/docs/architecture/DATABASE_SCHEMA.md	Explicit schema/migration descriptions and qualified verification status.	Its application tables as GEWU's model. Its dated local schema document is not evidence of current production state.
AAA/docs/architecture/BELIEFS_V2_CONTRACT.md	Separate encounter/assessment/decision records, digest bindings, explicit authority, immutable assessments and structured missing context.	Human adoption of every record. GEWU explicitly requires eligible automatic acceptance.
AAA/docs/architecture/BELIEFS_V2_PLAN.md	Preserve dissent, scope and revisions; similarity alone cannot establish equivalence or support.	Belief mass, participation/dream mechanics or a new internal reasoning layer.
Jev/.agents/protocols/cross-platform-acceptance-protocol.md	Per-OS/harness evidence, safe isolated fixtures, explicit result labels and configuration/connection/workflow distinctions.	Treating historical receipts or another client's pass as present compatibility.
Jev/.agents/protocols/documentation-standard-protocol.md	Progressive detail, one authoritative home per rule, a navigation hub and relative internal links.	Mandatory cmd /c/%CD% wrappers described as portable; mandatory metaphors, fixed RFC taxonomy or screenshot counts. Commands must name their shell and be tested.
Jev/.agents/protocols/style-protocol.md	Direct prose, concrete mechanisms, explicit limitations and respect for readers.	Mandatory author impersonation, philosophical slogans or rhetorical devices as engineering rules.
Jev/.agents/protocols/anti-slop-protocol.md	Remove hype, decorative prose and repetitive document structure while preserving exact constraints.	Word bans that erase useful technical distinctions or measurements.
Jev/.agents/protocols/system-one-balance-protocol.md	Context-aware follow-ups, proportionate process and avoiding repeated permission requests for authorized routine work.	Fail-open acceptance/security, model-confidence authority, routing thresholds or hook latency targets. Deterministic evidence and authority gates fail closed.
SonificationV2/docs/UI_DESIGN_PROTOCOL.md	Intentional editorial/technical type roles, curated tokens, coherent component grammar and explicit visual review.	CRT fringing/glow, uppercase operational text, tiny controls, DSP meters and instrumentation symbols unrelated to knowledge reading.

Contradictions resolved in the proposal

1. AAA's database is operationally central; GEWU requires Git-backed knowledge and a disposable search index. Durable proposals, receipts, artifacts and auth must therefore be explicitly outside the disposable index.
2. AAA's belief decisions begin with human adoption; GEWU permits routine same-agent support assessments and policy acceptance. Preserve attributable decisions without importing mandatory human review for every note.
3. Jev's workflow guidance favors routine speed and advisory fallback. In GEWU, search can degrade to keyword mode, but missing evidence or authority cannot degrade into successful acceptance.
4. The references optimize for agent telemetry and artistic instrumentation. The owner selected warm editorial reading for GEWU. Preserve rigor in evidence presentation while making content readable at ordinary sizes.
5. Local files support inspectability, but unrestricted agent access conflicts with enforced proposal-only writes. Separate service storage/identity from development and agent execution; report unenforced development mode honestly.

Resulting documents

The architecture chooses the proposed stack and runtime boundaries. The acceptance contract makes recovery, authority and evidence behavior reviewable. The development, visual, agent/security and operations protocols adapt the useful practices to GEWU.

The existing implementation-reference review remains relevant prior work for Jev/Winnow. Its probes were not rerun here. This review did not inspect or modify production databases or external repositories and does not claim their code implements every statement in their guides.