tylerg/auth-yes
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
auth-yes/AGENTS.md
Tyler Gillispie 474cc177ce chore: adopt dual licensing and import task history & scaffolding 
- Add LICENSE-MIT and LICENSE-APACHE for dual MIT / Apache-2.0 distribution
- Update root LICENSE pointer, README.md, Deno workspace manifests, and Cargo.toml
- Add deno.lock dependency lockfile
- Format AGENTS.md system guidelines
- Import task lifecycle scaffolding and historical story specifications (extract-auth-yes, setup-ts architecture, modular workspace)
2026-08-21 15:20:36 -07:00

1.3 KiB
Raw Blame History

AGENTS.md — Auth-Yes System Guidelines & Operating Protocol

1. Project Context

Auth-Yes is a standalone, ultra-low-friction, zero-trust Identity and Access Management (IAM) fabric and WebAuthn Passkey authority.

  • Runtime: Deno 2.x (TypeScript 5.x)
  • Architecture: Modular Deno Workspace (sdk/, server/, ui/, spire_ffi/, infra/)
  • Web API & SSR: Hono with pure Hono SSR JSX (Strictly React-free)
  • Workload Mesh: ConnectRPC daemon + Rust SPIFFE/mTLS FFI crate (spire_ffi/)
  • Data Layer: Dedicated PostgreSQL 18 + Valkey 8 (L1/L2 RESP3 Client Tracking)
  • Cookie Scope: Wildcard .atyg.org domain scoping with host-collision sweep

2. Key Architecture Standards

  1. Zero-Dependency SDK: @auth-yes/sdk must remain 100% free of backend/database imports. ConnectRPC contracts live in sdk/gen/.
  2. Security: Session invalidation and revocation MUST always be handled server-side (deleteCookie across host and wildcard domains).
  3. Quality Gates: Every PR must pass deno fmt, deno task lint, deno task check, and deno test.

3. History & Context Link

This repository was cleanly extracted from ed-droid.