Skip to content

Latest commit

 

History

History
54 lines (45 loc) · 2.46 KB

ARCHITECTURE.md

File metadata and controls

54 lines (45 loc) · 2.46 KB

Architecture

flowchart TD
    Browser[Job seekers, employers and editors] --> Web[Next.js pages and route handlers]
    Web --> Domain[Authentication, listings, billing and calendars]
    Domain --> DB[(SQLite)]
    Domain --> Stripe[Stripe Checkout and signed webhooks]
    Domain --> Outbox[(Durable email outbox)]
    Worker[Email worker] --> Outbox
    Worker --> Email[Configured email provider]
    Web --> Resources[External resource catalog]
    API[Public API and remote MCP] --> Public[Allowlisted public listing service]
    Public --> DB
    CLI[CLI and local MCP] --> API
    Backup[Online backup and integrity check] --> DB
Loading

Boundaries

Boundary Implementation
Browser mutations Canonical-origin checks, bounded input, authentication or scoped guest access, rate limiting
Account ownership Password hashing, hashed sessions, purpose-scoped recovery and verification
Paid publication Server-side prices, verified payment entitlement, separate editorial approval, expiry
Guest management Random capability in a fragment, hashed storage, restricted cookie and object scope
Public integrations Explicit output schemas; private and inactive records excluded
Messaging Confirmed consent, durable outbox, deduplication and suppression
Runtime storage SQLite and resource catalogs outside source control

Employer posting

sequenceDiagram
    participant E as Employer
    participant A as Application
    participant S as Stripe
    participant R as Editor
    E->>A: Create draft and save private capability
    E->>A: Request checkout
    A->>S: Server-priced, idempotent Checkout session
    S->>A: Signed event or server-verified session
    A->>A: Record entitlement and review state
    R->>A: Review and approve
    A->>A: Publish with expiry
Loading

The checkout return URL alone never proves payment or grants management access. Edits require the current listing version and revoke prior approval.

Deployment model

A single Node.js application binds to loopback behind the HTTPS edge. Immutable release directories contain source, dependencies and build output. Persistent data and environment secrets live outside those directories. A code rollback and a database restore are separate operations.

The public repository's systemd files are generic examples. GitHub Actions runs tests, type checking and a production build; it has no deployment credentials or connection to the running Azure service.