How NORDON Works Under the Hood

Stored memory example

<nordon-context>
  <memory type="fact" importance="0.75">
  ## Tech Stack
  - Backend: Node.js 20 + Express 4.18
  - Database: PostgreSQL 15, hosted on AWS RDS
  - Frontend: React 18 + Next.js 14 (App Router)
  - Auth: Clerk (migrated from Auth0 in Q3 2025)
  - API base URL: https://api.acme.com/v2
</memory>
</nordon-context>

Stored memory example

<nordon-context>
  <memory type="decision" importance="0.9">
  ## REST over GraphQL
  Chose REST for API layer. Benchmarks showed 3x better
  performance on read-heavy workload with proper caching.
  GraphQL added complexity without clear benefit at our scale.
  Decision date: 2025-11-15. Approved by: entire backend team.
</memory>
</nordon-context>

Stored memory example

<nordon-context>
  <memory type="procedure" importance="0.85">
  ## Database Migration Workflow
  1. Create migration: npx prisma migrate dev --name descriptive_name
  2. Review generated SQL in prisma/migrations/
  3. Test: npm run test:db
  4. PR must include migration file + updated schema.prisma
  5. On merge: CI auto-runs prisma migrate deploy
  IMPORTANT: Never modify an existing migration file.
</memory>
</nordon-context>

Stored memory example

<nordon-context>
  <memory type="failure" importance="0.92">
  ## OOM crash in image processing pipeline
  Symptom: Worker pods killed after processing batch of 50+ images.
  Root cause: Sharp library loads full image into memory for resize.
  Fix: Stream-based processing with pipeline(), limit concurrency
  to 5 images. See PR #892.
  Trigger: Any code that processes images in bulk.
</memory>
</nordon-context>

Stored memory example

<nordon-context>
  <memory type="pattern" importance="0.78">
  ## API Error Response Format
  All API errors must follow this shape:
  { error: { code: "RESOURCE_NOT_FOUND", message: "...",
    details?: {...} } }
  HTTP status codes: 400 validation, 401 auth, 403 forbidden,
  404 not found, 409 conflict, 500 internal.
  Never expose stack traces in production responses.
</memory>
</nordon-context>

Stored memory example

<nordon-context>
  <memory type="constraint" importance="0.95">
  ## PCI Compliance Requirements
  - Credit card numbers must NEVER be logged, even partially
  - All payment data encrypted at rest (AES-256)
  - Payment endpoints require mTLS
  - Audit log retention: minimum 7 years
  - Third-party payment SDKs must be on approved vendor list
  Violation = security incident. No exceptions.
</memory>
</nordon-context>

Stored memory example

<nordon-context>
  <memory type="context" importance="0.80">
  ## Active Migration: Monolith to Microservices
  Status: Phase 2 of 4 (extracting UserService)
  - Phase 1 (done): Extracted AuthService
  - Phase 2 (in progress): Extracting UserService
  - Phase 3 (planned): Extracting OrderService
  - Phase 4 (planned): Decommission monolith
  All new code should target the service boundaries defined
  in docs/architecture/service-map.md
</memory>
</nordon-context>