Add logging standards documentation with BetterStack reference and JWT signing standards

[Copilot]

Establishes formal logging standards for the CROW platform by adding a dedicated reference document and documents JWT signing standards in the system architecture.

Changes

• New document: docs/reference/logging-standards.md

  • References BetterStack's log formatting guide as the canonical standard
  • Defines structured JSON logging format with required fields (requestId, userId, service, duration)
  • Specifies log levels (ERROR, WARN, INFO, DEBUG) and their usage
  • Documents security requirements (no PII, credentials, or tokens in logs)
  • Links to existing Axiom integration and related documentation

• Updated document: docs/architecture/system-architecture.md

  • Added JWT signing standards to the Authentication section's JWT Tokens subsection:
    • System JWT: HS256 with shared secret
    • User JWT: RS256 via JWKS from Better Auth

Context

Structured logging requirements exist across multiple docs (microservices architecture, requirements FR37, coding conventions) but lacked a single authoritative reference. This consolidates logging standards in one location. JWT signing standards were previously undocumented and are now properly documented in the system architecture's authentication section.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[cloudflare-workers-and-pages]

Deploying internal-docs with    Cloudflare Pages

Latest commit:	2a963b9
Status:	✅  Deploy successful!
Preview URL:	https://ea7d89f8.internal-docs-ai1.pages.dev
Branch Preview URL:	https://copilot-add-logging-referenc.internal-docs-ai1.pages.dev

View logs

[prdai]

@copilot also mention the following is our security for the jwts we have

// System JWT: HS256 with shared secret

// User JWT: RS256 via JWKS from Better Auth

[Copilot]

@copilot also mention the following is our security for the jwts we have

// System JWT: HS256 with shared secret

...

Added JWT authentication standards to the Security section. The document now includes:

• System JWT: HS256 with shared secret
• User JWT: RS256 via JWKS from Better Auth

Also added guidance that tokens should never be logged in full, only metadata. (commit: cfd78e3)

[prdai]

@copilot also mention the following is our security for the jwts we have

// System JWT: HS256 with shared secret

...

Added JWT authentication standards to the Security section. The document now includes:

* System JWT: HS256 with shared secret

* User JWT: RS256 via JWKS from Better Auth

Also added guidance that tokens should never be logged in full, only metadata. (commit: cfd78e3)

@copilot this is not related to logging

[Copilot]

@copilot also mention the following is our security for the jwts we have

// System JWT: HS256 with shared secret

...

You're right - removed the JWT authentication standards section from the logging standards document. (commit: 1b66722)

[prdai]

@copilot also mention the following is our security for the jwts we have

// System JWT: HS256 with shared secret

...

You're right - removed the JWT authentication standards section from the logging standards document. (commit: 1b66722)

@copilot but add it where ever it is necssary man sigh

[Copilot]

@copilot also mention the following is our security for the jwts we have

// System JWT: HS256 with shared secret

...

Added JWT signing standards to the System Architecture document's Authentication section under "JWT Tokens":

• System JWT: HS256 with shared secret
• User JWT: RS256 via JWKS from Better Auth

(commit: 2a963b9)