From 098a2098f87169a2cf8a21f9204dd0e0bae19dd2 Mon Sep 17 00:00:00 2001 From: Rene Nochebuena Guerrero Date: Fri, 29 May 2026 15:43:08 +0000 Subject: [PATCH] feat(contracts): initial implementation (v1.0.0) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Introduces code.nochebuena.dev/einherjar/contracts — the zero-dependency foundation of the Einherjar framework. Defines the interfaces and minimal types consumed by every starter. Zero external dependencies. Zero Einherjar dependencies. Nothing is above it in the dependency graph. lifecycle: - Component — OnInit, OnStart, OnStop three-phase lifecycle hooks observability: - Level (LevelCritical=0, LevelDegraded); zero value is the safe default - Checkable — HealthCheck, Name, Priority - Identifiable — ModulePath, ModuleVersion; implemented by all starters to surface module identity and version in the startup banner logging: - Logger — Debug, Info, Warn, Error, With, WithContext errs: - CodedError — ErrorCode() string; satisfied by core/xerrors.Err - ContextualError — ErrorContext() map[string]any; satisfied by core/xerrors.Err security: - Identity value type — UID, TenantID, DisplayName, Email; NewIdentity, WithTenant - Permission (int64), MaxPermission=62, PermissionMask — Has, Grant - PermissionProvider — ResolveMask(ctx, uid, resource) (PermissionMask, error) - SecurityBag value type — immutable request-scoped security context; carries Identity and arbitrary typed attributes (hardware IDs, grant codes, etc.); With copies the attribute map on every call to preserve receiver-invariant behaviour - NewSecurityBag, Identity, WithIdentity, Get, With - SetBagInContext / BagFromContext — full bag context storage - SetInContext / FromContext — backed by SecurityBag; all four cross-function combinations (SetInContext+BagFromContext, SetBagInContext+FromContext) are valid One file per type; CT-6 enforced by compliance test AST walk. --- .gitea/CODEOWNERS | 1 + .gitea/pull_request_template.md | 70 +++ .gitignore | 35 ++ CHANGELOG.md | 165 ++++++ CLA.md | 90 +++ CONTRIBUTING.md | 247 +++++++++ LICENSE | 661 +++++++++++++++++++++++ README.md | 137 +++++ compliance_test.go | 301 +++++++++++ doc.go | 5 + docs/adr/ADR-001-errs-sub-package.md | 102 ++++ docs/adr/ADR-002-file-per-type-naming.md | 78 +++ docs/adr/index.md | 11 + errs/coded_error.go | 12 + errs/contextual_error.go | 12 + errs/doc.go | 4 + go.mod | 3 + lifecycle/component.go | 18 + lifecycle/doc.go | 3 + logging/doc.go | 3 + logging/logger.go | 26 + observability/checkable.go | 17 + observability/doc.go | 3 + observability/identifiable.go | 14 + observability/level.go | 15 + security/doc.go | 4 + security/identity.go | 75 +++ security/permission.go | 19 + security/permission_mask.go | 26 + security/permission_provider.go | 18 + security/security_bag.go | 55 ++ 31 files changed, 2230 insertions(+) create mode 100644 .gitea/CODEOWNERS create mode 100644 .gitea/pull_request_template.md create mode 100644 .gitignore create mode 100644 CHANGELOG.md create mode 100644 CLA.md create mode 100644 CONTRIBUTING.md create mode 100644 LICENSE create mode 100644 README.md create mode 100644 compliance_test.go create mode 100644 doc.go create mode 100644 docs/adr/ADR-001-errs-sub-package.md create mode 100644 docs/adr/ADR-002-file-per-type-naming.md create mode 100644 docs/adr/index.md create mode 100644 errs/coded_error.go create mode 100644 errs/contextual_error.go create mode 100644 errs/doc.go create mode 100644 go.mod create mode 100644 lifecycle/component.go create mode 100644 lifecycle/doc.go create mode 100644 logging/doc.go create mode 100644 logging/logger.go create mode 100644 observability/checkable.go create mode 100644 observability/doc.go create mode 100644 observability/identifiable.go create mode 100644 observability/level.go create mode 100644 security/doc.go create mode 100644 security/identity.go create mode 100644 security/permission.go create mode 100644 security/permission_mask.go create mode 100644 security/permission_provider.go create mode 100644 security/security_bag.go diff --git a/.gitea/CODEOWNERS b/.gitea/CODEOWNERS new file mode 100644 index 0000000..3a6b985 --- /dev/null +++ b/.gitea/CODEOWNERS @@ -0,0 +1 @@ +* @einherjar/CoreDevelopers @einherjar/Agents diff --git a/.gitea/pull_request_template.md b/.gitea/pull_request_template.md new file mode 100644 index 0000000..1bf0362 --- /dev/null +++ b/.gitea/pull_request_template.md @@ -0,0 +1,70 @@ +## Summary + + + +--- + +## Type of change + +- [ ] Bug fix — non-breaking change that resolves an issue +- [ ] New feature — non-breaking addition of functionality +- [ ] Breaking change — alters existing behavior or public API +- [ ] Documentation update +- [ ] Refactor — no functional change, no new API surface +- [ ] Test improvement + +--- + +## Description + + + +--- + +## Testing + +- [ ] I added or updated tests that cover my changes +- [ ] All tests pass locally — `go test ./...` +- [ ] No formatting issues — `gofmt -l .` produces no output +- [ ] No vet warnings — `go vet ./...` is clean + +--- + +## Checklist + +- [ ] At most one exported type per non-test `.go` file (CT-6) +- [ ] No new external dependencies added without prior discussion in an issue +- [ ] Public API changes are reflected in `CHANGELOG.md` +- [ ] Breaking changes include a migration note in the PR description above + +--- + +## Contributor License Agreement + +> **This PR will not be merged until the CLA comment is present.** + +Before a Maintainer reviews your code, you must post the following text **as a comment on this PR** — not here in the description. PR description checkboxes can be silently toggled by anyone; a comment is a timestamped, author-attributed record that cannot be quietly removed. + +**Copy and post this exact text as a PR comment:** + +--- + +> I have read the Einherjar Contributor License Agreement (CLA.md) and I agree to all its terms. +> I confirm this Contribution is my original work. I grant the Maintainers the rights described +> therein, including the right to relicense, and I retain ownership of my copyright. +> This agreement covers all future Contributions I submit to any Einherjar repository under +> this account. + +--- + +First time contributing? Read [CLA.md](../CLA.md) for the full agreement before posting the comment. + +If you are contributing on behalf of a company, an authorized representative of that company must post the comment. + + diff --git a/.gitignore b/.gitignore new file mode 100644 index 0000000..8d26673 --- /dev/null +++ b/.gitignore @@ -0,0 +1,35 @@ +# ── Release workflow helpers ────────────────────────────────────────────────── +COMMIT.md +PR.md +RELEASE.md + +# ── Go build artifacts ──────────────────────────────────────────────────────── +*.exe +*.exe~ +*.dll +*.so +*.dylib +*.test +*.out + +# ── Go workspace (local multi-module dev only) ──────────────────────────────── +go.work +go.work.sum + +# ── Dependency vendoring (not used in Einherjar modules) ───────────────────── +vendor/ + +# ── Test & coverage output ──────────────────────────────────────────────────── +coverage.html +coverage.txt + +# ── OS artifacts ───────────────────────────────────────────────────────────── +.DS_Store +Thumbs.db + +# ── Editor artifacts ────────────────────────────────────────────────────────── +.idea/ +.vscode/ +*.swp +*.swo +*~ diff --git a/CHANGELOG.md b/CHANGELOG.md new file mode 100644 index 0000000..011ac09 --- /dev/null +++ b/CHANGELOG.md @@ -0,0 +1,165 @@ +# Changelog + +All notable changes to this module will be documented in this file. + +The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), +and this module adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). + +--- + +## [1.1.0] — 2026-05-28 + +### Added + +**`security`** + +- `SecurityBag` struct — request-scoped security context that carries both the + authenticated `Identity` and arbitrary string-keyed attributes injected during + the enrichment phase (e.g. hardware IDs, grant codes). Value type — all mutation + methods return a new value without modifying the receiver. The attribute map is + copied on every `With` call to preserve immutability guarantees. +- `NewSecurityBag(id Identity) SecurityBag` — constructs a `SecurityBag` wrapping + the given Identity with an empty attribute map +- `SecurityBag.Identity() Identity` — returns the authenticated Identity stored in + the bag +- `SecurityBag.WithIdentity(id Identity) SecurityBag` — returns a copy of the bag + with the Identity replaced; used by bag enrichers that modify the Identity (e.g. + applying a tenant ID from a request header) +- `SecurityBag.Get(key string) (any, bool)` — returns the attribute stored under + key, or `(nil, false)` if absent +- `SecurityBag.With(key string, value any) SecurityBag` — returns a copy of the + bag with the given key set to value; the receiver is not modified +- `SetBagInContext(ctx context.Context, bag SecurityBag) context.Context` — stores + the full `SecurityBag` in ctx; use instead of `SetInContext` when extra attributes + need to travel alongside the Identity +- `BagFromContext(ctx context.Context) (SecurityBag, bool)` — retrieves the + `SecurityBag` stored by `SetBagInContext` or `SetInContext`; permission providers + use this to access both the Identity and any enrichment attributes + +### Changed + +**`security`** + +- `SetInContext` — now stores a `SecurityBag` wrapping the Identity internally, + replacing direct `Identity` storage. The function signature is **unchanged**; + all existing callers continue to work without modification. +- `FromContext` — now extracts the Identity from the stored `SecurityBag` + internally. The function signature is **unchanged**; all existing callers + continue to work without modification. `SetBagInContext` + `FromContext` is + valid (returns the bag's Identity). `SetInContext` + `BagFromContext` is valid + (returns a bag wrapping the identity with an empty attribute map). + +### Design Notes + +- `SecurityBag` is additive — no existing interface or function signature is + modified. Starters compiled against v1.0.0 continue to work against v1.1.0 + without any code changes. +- The framework defines no string key constants for bag attributes. All + framework-known fields are typed fields on `Identity`. Callers define their + own constants to avoid collisions and maintain compile-time safety at the + type-assertion call site. + +--- + +## [1.0.0] — 2026-05-27 + +### Added + +**`lifecycle`** + +- `Component` interface — `OnInit() error` (open connections, allocate resources), + `OnStart() error` (start background goroutines and listeners), `OnStop() error` + (graceful shutdown and resource release); the framework calls these in strict + phase order and shuts down components in reverse registration order + +**`observability`** + +- `Level` type — `int`-based criticality classifier for health reporting; zero value + is `LevelCritical`, making it a safe default for any component that forgets to set it +- `LevelCritical` constant — marks a component essential to application function; + a failing critical component sets overall health to DOWN (HTTP 503) +- `LevelDegraded` constant — marks a component important but not essential; a failing + degraded component sets overall health to DEGRADED (HTTP 200), not DOWN +- `Checkable` interface — `HealthCheck(ctx context.Context) error` (connectivity or + liveness probe), `Name() string` (display name in health responses), `Priority() Level` + (criticality of this component); implemented by all infrastructure components; + consumed by the `web` starter's health handler without the data layer ever importing HTTP + +**`logging`** + +- `Logger` interface — `Debug`, `Info`, `Warn(msg string, args ...any)`, `Error(msg string, err error, args ...any)`, + `With(args ...any) Logger`, `WithContext(ctx context.Context) Logger`; all Einherjar + starters accept `Logger` at their constructors and pass it to sub-components — never + the concrete implementation; `Error` treats `err` as a first-class parameter to enable + automatic enrichment from `errs.CodedError` and `errs.ContextualError` + +**`errs`** + +- `CodedError` interface — `ErrorCode() string`; implemented by structured errors that + carry a machine-readable SCREAMING_SNAKE_CASE code meaningful to frontend consumers; + consumed by the `core` logger to append `error_code` automatically to every log record + where the error satisfies this interface; internal or infrastructure errors must not + carry a code — those get a generic fallback on the frontend +- `ContextualError` interface — `ErrorContext() map[string]any`; implemented by + structured errors that carry key-value context fields; consumed by the `core` logger + to append all context fields to the log record automatically; the returned map must + not be modified by the caller + +**`security`** + +- `Identity` struct — `UID`, `TenantID`, `DisplayName`, `Email string`; value type, + always copied never a pointer, preventing nil-check burden and accidental mutation + across concurrent middleware +- `NewIdentity(uid, displayName, email string) Identity` — constructs an Identity from + token authentication data; `TenantID` is intentionally left empty for enrichment + in a later middleware step +- `Identity.WithTenant(id string) Identity` — returns a copy of the Identity with + `TenantID` set; the receiver is not mutated, safe to call from concurrent middleware +- `SetInContext(ctx context.Context, id Identity) context.Context` — stores an Identity + in the context using a package-private key type, preventing collisions with keys from + other packages +- `FromContext(ctx context.Context) (Identity, bool)` — retrieves the Identity stored by + `SetInContext`; returns the zero-value Identity and false if no identity is present +- `Permission` type — named `int64` bit position (0–62) representing a single + capability; applications define their own domain constants using this type +- `MaxPermission` constant — highest valid bit position (62); bit 63 is reserved for + the sign bit of the underlying `int64` +- `PermissionMask` type — resolved `int64` bit-mask for a user on a specific resource; + zero value means no permissions granted +- `PermissionMask.Has(p Permission) bool` — reports whether the given permission bit + is set; returns false for out-of-range values (p < 0 or p > MaxPermission) +- `PermissionMask.Grant(p Permission) PermissionMask` — returns a new mask with the + bit for p set; the receiver is not modified, safe to use in builder chains +- `PermissionProvider` interface — `ResolveMask(ctx context.Context, uid, resource string) (PermissionMask, error)`; + implementations may call `FromContext` to retrieve the Identity and its TenantID + when multi-tenancy is required + +### Design Notes + +- `contracts` has zero external dependencies and zero Einherjar dependencies. Its + `go.mod` requires nothing beyond the Go standard library. If adding something to + `contracts` requires a new `require` entry, it does not belong in `contracts`. + +- Changes flow outward from `contracts`, never inward. A starter never drives a + contracts change. Before any modification, the blast radius is calculated: which + interfaces are affected → which starters implement them → which starters consume + those starters. Release sequence: `contracts` first, then implementors, then + consumers. + +- The `errs` sub-package formalises a contract that previously existed only as + private duck-typed interfaces inside micro-lib's `logz`. The two interfaces are + intentionally separate (`CodedError` and `ContextualError` rather than one combined + `RichError`) to honour ISP: an error may carry a code but no context fields, or + context fields but no code. Implementors are never forced to provide both. + +- `Checkable` lives in `contracts/observability`, not in the `web` starter. Data + starters (`db-postgres`, `db-sqlite`, etc.) implement `Checkable` without importing + the HTTP layer. The health handler in `web` consumes `Checkable` — the dependency + arrow points into the data layer, never out. + +- Every file in `contracts` exports exactly one type or interface. This is enforced + structurally and mechanically by the compliance test using `go/ast` parsing. A + reviewer reading `permission_mask.go` knows exactly what they are reading without + opening any other file. + +[1.0.0]: https://code.nochebuena.dev/einherjar/contracts/releases/tag/v1.0.0 diff --git a/CLA.md b/CLA.md new file mode 100644 index 0000000..2850689 --- /dev/null +++ b/CLA.md @@ -0,0 +1,90 @@ +# Contributor License Agreement + +By contributing to any Einherjar repository, you agree to the terms of this Contributor License Agreement ("Agreement"). Please read it carefully before submitting your first Pull Request. + +--- + +## 1. Definitions + +| Term | Meaning | +|---|---| +| **You** | The individual or legal entity submitting a Contribution | +| **Contribution** | Any original work — source code, documentation, tests, configuration — submitted to an Einherjar repository | +| **Project** | The Einherjar framework and all repositories under `code.nochebuena.dev/einherjar/` | +| **Maintainers** | The individuals responsible for maintaining the Project | + +--- + +## 2. You Retain Ownership + +This Agreement does **not** transfer your copyright to the Maintainers. You remain the legal owner of your Contribution. What you grant here is a broad license to use it — not ownership of it. + +--- + +## 3. Copyright License Grant + +You grant the Maintainers and all recipients of the Project a **perpetual, worldwide, non-exclusive, royalty-free, irrevocable** license to: + +- Reproduce, modify, and create derivative works of your Contribution +- Publicly display and perform your Contribution +- Distribute your Contribution and derivative works, in source or compiled form, under any terms +- Sublicense the above rights to third parties +- **Relicense** your Contribution under a different open-source or commercial license at the Maintainers' sole discretion + +The Maintainers commit to keeping the Project available under at least one OSI-approved open-source license at all times. + +--- + +## 4. Patent License Grant + +You grant the Maintainers and all recipients of the Project a **perpetual, worldwide, non-exclusive, royalty-free, irrevocable** patent license to make, use, sell, offer for sale, import, and distribute your Contribution — limited to patent claims you own or control that are necessarily infringed by your Contribution alone, or in combination with the Project to which you submitted it. + +--- + +## 5. Your Representations + +By submitting a Contribution, you confirm that: + +1. **Original work.** The Contribution is your original work, or you have the legal right to submit it under these terms. +2. **No infringement.** To your knowledge, the Contribution does not infringe any third-party intellectual property rights, including patents, copyrights, and trade secrets. +3. **Employer rights.** If your employer holds rights over intellectual property you create, you have obtained written permission to submit the Contribution on behalf of that employer, or your employer has explicitly waived such rights for contributions to open-source projects. +4. **No warranty implied.** You understand that your Contribution may or may not be included in the Project, and the Maintainers are under no obligation to use it. + +--- + +## 6. No Support Obligation + +You are not required to provide maintenance, support, or updates for your Contributions. They are accepted **"as-is"**, without any warranty of fitness for a particular purpose or correctness. + +--- + +## 7. How to Sign + +Consent is given by **posting a comment** on your Pull Request with the following exact text: + +``` +I have read the Einherjar Contributor License Agreement (CLA.md) and I agree to all its terms. +I confirm this Contribution is my original work. I grant the Maintainers the rights described +therein, including the right to relicense, and I retain ownership of my copyright. +This agreement covers all future Contributions I submit to any Einherjar repository under +this account. +``` + +**Why a comment and not a checkbox?** +PR description checkboxes can be silently toggled on and off by anyone with write access to the branch at any time. A comment creates a timestamped, author-attributed record in the PR activity log — it cannot be quietly retracted. If a comment is deleted, the deletion itself is visible in the activity log. + +No handwritten or electronic signature is required beyond the comment above. A Maintainer will verify the comment before merging. PRs without the comment will not be merged. + +If you are contributing on behalf of a company or organization, ensure that an authorized representative of that entity has reviewed and accepted these terms before submitting. The comment must be posted by the account that owns the Contribution. + +--- + +## 8. Governing Terms + +This Agreement is intended to be simple and broadly fair. It follows the model established by widely adopted CLAs from the Apache Software Foundation, Google, and MongoDB — granting the Project the flexibility to evolve while fully preserving your ownership of what you wrote. + +If any provision of this Agreement is found unenforceable, the remaining provisions continue in full effect. + +--- + +*For those who come after. — The Einherjar Maintainers* diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md new file mode 100644 index 0000000..ed3e1d0 --- /dev/null +++ b/CONTRIBUTING.md @@ -0,0 +1,247 @@ +# Contributing to Einherjar + +Thank you for your interest in contributing to Einherjar. This document explains everything you need to know before sending your first Pull Request. + +Einherjar is developed and maintained by **NOCHEBUENADEV**, the trade name of its founder operating as a *Persona Física con Actividad Empresarial* (PFAE) under Mexican law. Contributions are welcome and valued — but they are accepted under the terms described here, so please read this document fully before you begin. + +--- + +## Table of Contents + +1. [Before You Start](#1-before-you-start) +2. [Legal: CLA and Copyright](#2-legal-cla-and-copyright) +3. [Development Setup](#3-development-setup) +4. [Code Standards](#4-code-standards) +5. [Commit Messages](#5-commit-messages) +6. [Submitting a Pull Request](#6-submitting-a-pull-request) +7. [Reporting Bugs](#7-reporting-bugs) +8. [Requesting Features](#8-requesting-features) +9. [What Gets Accepted](#9-what-gets-accepted) + +--- + +## 1. Before You Start + +**Open an issue first for anything non-trivial.** + +Before you write a line of code, open an issue describing what you want to change and why. This protects your time: a change that seems straightforward may conflict with a planned refactor, an architectural decision, or the project's direction. Getting alignment before coding means your PR will not be rejected for reasons unrelated to its quality. + +Exceptions where you can skip the issue: +- Typo or documentation-only fix +- Test coverage improvement for existing behavior +- Trivially obvious bug with a clear, contained fix + +**Do not submit a PR that changes the public API of any module without prior discussion.** Every Einherjar module has a stability contract. Breaking changes require a major version bump and coordinated updates across dependent modules. + +--- + +## 2. Legal: CLA and Copyright + +### Contributor License Agreement + +Before your first PR can be merged, you must sign the Contributor License Agreement by **posting a specific comment** on your Pull Request. The required comment text and full instructions are in [CLA.md](CLA.md). + +> Checkboxes in PR descriptions are not used for CLA consent — they can be silently toggled by anyone. A comment is a timestamped, author-attributed record. + +### Copyright + +All original code in Einherjar is copyright **NOCHEBUENADEV**. NOCHEBUENADEV is the registered trade name of its founder, a natural person operating under the Mexican *Persona Física con Actividad Empresarial* (PFAE) regime. + +When you contribute, you retain ownership of what you wrote. By signing the CLA you grant NOCHEBUENADEV a perpetual, irrevocable, worldwide license to use, modify, sublicense, and redistribute your Contribution — including the right to relicense it. See [CLA.md](CLA.md) for the full terms. + +### License + +Einherjar is licensed under the **GNU Affero General Public License v3.0** (AGPL-3.0). Your Contributions will be distributed under the same license unless the Maintainers exercise their relicensing rights under the CLA. + +--- + +## 3. Development Setup + +Einherjar uses a Go workspace (`go.work`) that spans all modules. You do not need to `go get` anything — local replacements are wired automatically. + +### Prerequisites + +- Go 1.26+ +- Git + +### Clone and initialize + +```bash +git clone https://code.nochebuena.dev/einherjar/ +cd + +# If working across multiple modules, clone the workspace root instead +# and all modules will resolve from disk via go.work. +``` + +### Verify your setup + +```bash +go build ./... # must compile clean +go vet ./... # no warnings +go test ./... # all tests pass +gofmt -l . # no output (no unformatted files) +``` + +All four commands must produce clean output before a PR will be reviewed. + +--- + +## 4. Code Standards + +These are non-negotiable. Every PR is checked against them. + +### One exported type per file (CT-6) + +Each non-test `.go` file may contain **at most one exported TypeSpec** (type, struct, or interface declaration). Unexported helpers, constants, and functions may coexist in the same file. `_test.go` files are exempt. + +This rule exists to keep the codebase navigable: a developer who knows the type name can immediately predict the file name. + +``` +provider.go ← type Provider interface { ... } ✓ one exported type +component.go ← type Component interface { ... } ✓ one exported type +new.go ← func New(...) + unexported impl ✓ zero exported types +``` + +### Formatting + +All code must be formatted with `gofmt`. No exceptions. If `gofmt -l .` produces output, the PR will not be merged. + +Do not configure your editor to use `goimports` as a replacement — it may add import groups that diverge from the project style. Use `gofmt` + manual import management. + +### Naming conventions + +- Follow standard Go naming: `CamelCase` for exported, `camelCase` for unexported. +- Interfaces that represent a capability are named with an agent noun: `Provider`, `Sender`, `Checkable`. +- Interfaces that represent a full component are named `Component`. +- Config structs are named `Config`. One config struct per module root. +- Constructors are named `New` (main) or `NewXxx` (adapters and variants). + +### Error handling + +- Use `core/xerrors` for all errors returned from public API. Never return raw `errors.New` or `fmt.Errorf` from exported functions. +- Error codes must map to the gRPC canonical set defined in `xerrors`. If you need a new code, open an issue first. +- Do not swallow errors silently. Log at the appropriate level or return them. + +### No comments unless necessary + +Do not add comments that restate what the code already says. Only add a comment when the **why** is non-obvious: a hidden constraint, a subtle invariant, a workaround for a known upstream bug. If removing the comment would not confuse a future reader, do not write it. + +### Dependencies + +Do not add new external dependencies without opening an issue and getting explicit approval first. Einherjar modules are deliberately lean. Every new dependency increases the blast radius for downstream consumers. + +--- + +## 5. Commit Messages + +Follow the [Conventional Commits](https://www.conventionalcommits.org/) specification: + +``` +(): + +[optional body] +``` + +| Type | When to use | +|---|---| +| `feat` | New exported function, type, or behavior | +| `fix` | Bug fix in existing behavior | +| `docs` | Documentation only | +| `test` | Tests only, no production code change | +| `refactor` | Code restructure with no behavior change | +| `chore` | Build system, CI, dependency updates | + +**Scope** is the module name without the `einherjar/` prefix: `core`, `web`, `db-postgres`, `cache-valkey`, etc. + +Examples: +``` +feat(cache-valkey): add IncrWithTTL for atomic fixed-window counters +fix(db-postgres): handle pgconn deadline exceeded as ErrDeadlineExceeded +docs(web): document rate limiter fail-open behavior +``` + +Keep the subject line under 72 characters. Write in the imperative mood ("add", "fix", "remove" — not "added", "fixes", "removed"). + +--- + +## 6. Submitting a Pull Request + +1. **Open an issue first** (see §1) unless the change is trivial. +2. Fork the repository and create a branch from `main`: + ```bash + git checkout -b feat/your-feature-name + ``` +3. Make your changes following the standards in §4. +4. Ensure all verification commands pass (§3). +5. Open the PR against `main` using the provided PR template. +6. **Post the CLA comment** on the PR before requesting review (see §2 and [CLA.md](CLA.md)). +7. Respond to review feedback. Keep the review cycle short by addressing all comments before re-requesting review. + +### Branch naming + +| Prefix | Use for | +|---|---| +| `feat/` | New features | +| `fix/` | Bug fixes | +| `docs/` | Documentation changes | +| `test/` | Test additions or improvements | +| `refactor/` | Refactors without behavior change | + +### PR size + +Keep PRs focused. A PR that does one thing is easier to review, faster to merge, and safer to revert if needed. If your change naturally spans multiple concerns, split it into multiple PRs. + +--- + +## 7. Reporting Bugs + +Open an issue with the following information: + +- **Module** affected (`einherjar/db-postgres`, `einherjar/web`, etc.) +- **Go version** (`go version`) +- **Minimal reproduction** — the smallest code snippet that demonstrates the problem +- **Expected behavior** vs **actual behavior** +- **Error output** if applicable (sanitize any credentials or sensitive data) + +Do not open a PR to fix a bug without first opening an issue. The bug may be intentional behavior, already fixed on `main`, or caused by something outside the module. + +--- + +## 8. Requesting Features + +Open an issue with: + +- **What** you want to add and **why** it belongs in the framework (not in application code) +- **Which module** it affects, or whether it requires a new module +- **API sketch** — what the interface, function signature, or config field would look like +- **Alternative approaches** you considered + +Feature requests that add a new external dependency, change a public interface, or cross module boundaries require longer discussion before approval. + +--- + +## 9. What Gets Accepted + +Einherjar is a **focused framework**. It covers a specific, well-defined set of infrastructure concerns. Contributions that fall outside that scope — however well-written — will not be merged. + +What fits: +- Bug fixes in existing behavior +- Performance improvements with benchmarks +- Missing error mappings for existing drivers +- Documentation improvements and example corrections +- Test coverage for untested edge cases + +What does not fit without prior architectural agreement: +- New modules (open an issue first) +- New external dependencies +- Changes to public interfaces in any module +- Features that belong in application code rather than the framework + +If you are unsure, open an issue and ask. It costs nothing and saves everyone time. + +--- + +*Einherjar was built for those who come after. Contributions that hold to that standard — clear, documented, tested, designed for the developer who was never in the room — are always welcome.* + +— **NOCHEBUENADEV** diff --git a/LICENSE b/LICENSE new file mode 100644 index 0000000..0ad25db --- /dev/null +++ b/LICENSE @@ -0,0 +1,661 @@ + GNU AFFERO GENERAL PUBLIC LICENSE + Version 3, 19 November 2007 + + Copyright (C) 2007 Free Software Foundation, Inc. + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. + + Preamble + + The GNU Affero General Public License is a free, copyleft license for +software and other kinds of works, specifically designed to ensure +cooperation with the community in the case of network server software. + + The licenses for most software and other practical works are designed +to take away your freedom to share and change the works. By contrast, +our General Public Licenses are intended to guarantee your freedom to +share and change all versions of a program--to make sure it remains free +software for all its users. + + When we speak of free software, we are referring to freedom, not +price. Our General Public Licenses are designed to make sure that you +have the freedom to distribute copies of free software (and charge for +them if you wish), that you receive source code or can get it if you +want it, that you can change the software or use pieces of it in new +free programs, and that you know you can do these things. + + Developers that use our General Public Licenses protect your rights +with two steps: (1) assert copyright on the software, and (2) offer +you this License which gives you legal permission to copy, distribute +and/or modify the software. + + A secondary benefit of defending all users' freedom is that +improvements made in alternate versions of the program, if they +receive widespread use, become available for other developers to +incorporate. Many developers of free software are heartened and +encouraged by the resulting cooperation. However, in the case of +software used on network servers, this result may fail to come about. +The GNU General Public License permits making a modified version and +letting the public access it on a server without ever releasing its +source code to the public. + + The GNU Affero General Public License is designed specifically to +ensure that, in such cases, the modified source code becomes available +to the community. It requires the operator of a network server to +provide the source code of the modified version running there to the +users of that server. Therefore, public use of a modified version, on +a publicly accessible server, gives the public access to the source +code of the modified version. + + An older license, called the Affero General Public License and +published by Affero, was designed to accomplish similar goals. This is +a different license, not a version of the Affero GPL, but Affero has +released a new version of the Affero GPL which permits relicensing under +this license. + + The precise terms and conditions for copying, distribution and +modification follow. + + TERMS AND CONDITIONS + + 0. Definitions. + + "This License" refers to version 3 of the GNU Affero General Public License. + + "Copyright" also means copyright-like laws that apply to other kinds of +works, such as semiconductor masks. + + "The Program" refers to any copyrightable work licensed under this +License. Each licensee is addressed as "you". "Licensees" and +"recipients" may be individuals or organizations. + + To "modify" a work means to copy from or adapt all or part of the work +in a fashion requiring copyright permission, other than the making of an +exact copy. The resulting work is called a "modified version" of the +earlier work or a work "based on" the earlier work. + + A "covered work" means either the unmodified Program or a work based +on the Program. + + To "propagate" a work means to do anything with it that, without +permission, would make you directly or secondarily liable for +infringement under applicable copyright law, except executing it on a +computer or modifying a private copy. Propagation includes copying, +distribution (with or without modification), making available to the +public, and in some countries other activities as well. + + To "convey" a work means any kind of propagation that enables other +parties to make or receive copies. Mere interaction with a user through +a computer network, with no transfer of a copy, is not conveying. + + An interactive user interface displays "Appropriate Legal Notices" +to the extent that it includes a convenient and prominently visible +feature that (1) displays an appropriate copyright notice, and (2) +tells the user that there is no warranty for the work (except to the +extent that warranties are provided), that licensees may convey the +work under this License, and how to view a copy of this License. If +the interface presents a list of user commands or options, such as a +menu, a prominent item in the list meets this criterion. + + 1. Source Code. + + The "source code" for a work means the preferred form of the work +for making modifications to it. "Object code" means any non-source +form of a work. + + A "Standard Interface" means an interface that either is an official +standard defined by a recognized standards body, or, in the case of +interfaces specified for a particular programming language, one that +is widely used among developers working in that language. + + The "System Libraries" of an executable work include anything, other +than the work as a whole, that (a) is included in the normal form of +packaging a Major Component, but which is not part of that Major +Component, and (b) serves only to enable use of the work with that +Major Component, or to implement a Standard Interface for which an +implementation is available to the public in source code form. A +"Major Component", in this context, means a major essential component +(kernel, window system, and so on) of the specific operating system +(if any) on which the executable work runs, or a compiler used to +produce the work, or an object code interpreter used to run it. + + The "Corresponding Source" for a work in object code form means all +the source code needed to generate, install, and (for an executable +work) run the object code and to modify the work, including scripts to +control those activities. However, it does not include the work's +System Libraries, or general-purpose tools or generally available free +programs which are used unmodified in performing those activities but +which are not part of the work. For example, Corresponding Source +includes interface definition files associated with source files for +the work, and the source code for shared libraries and dynamically +linked subprograms that the work is specifically designed to require, +such as by intimate data communication or control flow between those +subprograms and other parts of the work. + + The Corresponding Source need not include anything that users +can regenerate automatically from other parts of the Corresponding +Source. + + The Corresponding Source for a work in source code form is that +same work. + + 2. Basic Permissions. + + All rights granted under this License are granted for the term of +copyright on the Program, and are irrevocable provided the stated +conditions are met. This License explicitly affirms your unlimited +permission to run the unmodified Program. The output from running a +covered work is covered by this License only if the output, given its +content, constitutes a covered work. This License acknowledges your +rights of fair use or other equivalent, as provided by copyright law. + + You may make, run and propagate covered works that you do not +convey, without conditions so long as your license otherwise remains +in force. You may convey covered works to others for the sole purpose +of having them make modifications exclusively for you, or provide you +with facilities for running those works, provided that you comply with +the terms of this License in conveying all material for which you do +not control copyright. Those thus making or running the covered works +for you must do so exclusively on your behalf, under your direction +and control, on terms that prohibit them from making any copies of +your copyrighted material outside their relationship with you. + + Conveying under any other circumstances is permitted solely under +the conditions stated below. Sublicensing is not allowed; section 10 +makes it unnecessary. + + 3. Protecting Users' Legal Rights From Anti-Circumvention Law. + + No covered work shall be deemed part of an effective technological +measure under any applicable law fulfilling obligations under article +11 of the WIPO copyright treaty adopted on 20 December 1996, or +similar laws prohibiting or restricting circumvention of such +measures. + + When you convey a covered work, you waive any legal power to forbid +circumvention of technological measures to the extent such circumvention +is effected by exercising rights under this License with respect to +the covered work, and you disclaim any intention to limit operation or +modification of the work as a means of enforcing, against the work's +users, your or third parties' legal rights to forbid circumvention of +technological measures. + + 4. Conveying Verbatim Copies. + + You may convey verbatim copies of the Program's source code as you +receive it, in any medium, provided that you conspicuously and +appropriately publish on each copy an appropriate copyright notice; +keep intact all notices stating that this License and any +non-permissive terms added in accord with section 7 apply to the code; +keep intact all notices of the absence of any warranty; and give all +recipients a copy of this License along with the Program. + + You may charge any price or no price for each copy that you convey, +and you may offer support or warranty protection for a fee. + + 5. Conveying Modified Source Versions. + + You may convey a work based on the Program, or the modifications to +produce it from the Program, in the form of source code under the +terms of section 4, provided that you also meet all of these conditions: + + a) The work must carry prominent notices stating that you modified + it, and giving a relevant date. + + b) The work must carry prominent notices stating that it is + released under this License and any conditions added under section + 7. This requirement modifies the requirement in section 4 to + "keep intact all notices". + + c) You must license the entire work, as a whole, under this + License to anyone who comes into possession of a copy. This + License will therefore apply, along with any applicable section 7 + additional terms, to the whole of the work, and all its parts, + regardless of how they are packaged. This License gives no + permission to license the work in any other way, but it does not + invalidate such permission if you have separately received it. + + d) If the work has interactive user interfaces, each must display + Appropriate Legal Notices; however, if the Program has interactive + interfaces that do not display Appropriate Legal Notices, your + work need not make them do so. + + A compilation of a covered work with other separate and independent +works, which are not by their nature extensions of the covered work, +and which are not combined with it such as to form a larger program, +in or on a volume of a storage or distribution medium, is called an +"aggregate" if the compilation and its resulting copyright are not +used to limit the access or legal rights of the compilation's users +beyond what the individual works permit. Inclusion of a covered work +in an aggregate does not cause this License to apply to the other +parts of the aggregate. + + 6. Conveying Non-Source Forms. + + You may convey a covered work in object code form under the terms +of sections 4 and 5, provided that you also convey the +machine-readable Corresponding Source under the terms of this License, +in one of these ways: + + a) Convey the object code in, or embodied in, a physical product + (including a physical distribution medium), accompanied by the + Corresponding Source fixed on a durable physical medium + customarily used for software interchange. + + b) Convey the object code in, or embodied in, a physical product + (including a physical distribution medium), accompanied by a + written offer, valid for at least three years and valid for as + long as you offer spare parts or customer support for that product + model, to give anyone who possesses the object code either (1) a + copy of the Corresponding Source for all the software in the + product that is covered by this License, on a durable physical + medium customarily used for software interchange, for a price no + more than your reasonable cost of physically performing this + conveying of source, or (2) access to copy the + Corresponding Source from a network server at no charge. + + c) Convey individual copies of the object code with a copy of the + written offer to provide the Corresponding Source. This + alternative is allowed only occasionally and noncommercially, and + only if you received the object code with such an offer, in accord + with subsection 6b. + + d) Convey the object code by offering access from a designated + place (gratis or for a charge), and offer equivalent access to the + Corresponding Source in the same way through the same place at no + further charge. You need not require recipients to copy the + Corresponding Source along with the object code. If the place to + copy the object code is a network server, the Corresponding Source + may be on a different server (operated by you or a third party) + that supports equivalent copying facilities, provided you maintain + clear directions next to the object code saying where to find the + Corresponding Source. Regardless of what server hosts the + Corresponding Source, you remain obligated to ensure that it is + available for as long as needed to satisfy these requirements. + + e) Convey the object code using peer-to-peer transmission, provided + you inform other peers where the object code and Corresponding + Source of the work are being offered to the general public at no + charge under subsection 6d. + + A separable portion of the object code, whose source code is excluded +from the Corresponding Source as a System Library, need not be +included in conveying the object code work. + + A "User Product" is either (1) a "consumer product", which means any +tangible personal property which is normally used for personal, family, +or household purposes, or (2) anything designed or sold for incorporation +into a dwelling. In determining whether a product is a consumer product, +doubtful cases shall be resolved in favor of coverage. For a particular +product received by a particular user, "normally used" refers to a +typical or common use of that class of product, regardless of the status +of the particular user or of the way in which the particular user +actually uses, or expects or is expected to use, the product. A product +is a consumer product regardless of whether the product has substantial +commercial, industrial or non-consumer uses, unless such uses represent +the only significant mode of use of the product. + + "Installation Information" for a User Product means any methods, +procedures, authorization keys, or other information required to install +and execute modified versions of a covered work in that User Product from +a modified version of its Corresponding Source. The information must +suffice to ensure that the continued functioning of the modified object +code is in no case prevented or interfered with solely because +modification has been made. + + If you convey an object code work under this section in, or with, or +specifically for use in, a User Product, and the conveying occurs as +part of a transaction in which the right of possession and use of the +User Product is transferred to the recipient in perpetuity or for a +fixed term (regardless of how the transaction is characterized), the +Corresponding Source conveyed under this section must be accompanied +by the Installation Information. But this requirement does not apply +if neither you nor any third party retains the ability to install +modified object code on the User Product (for example, the work has +been installed in ROM). + + The requirement to provide Installation Information does not include a +requirement to continue to provide support service, warranty, or updates +for a work that has been modified or installed by the recipient, or for +the User Product in which it has been modified or installed. Access to a +network may be denied when the modification itself materially and +adversely affects the operation of the network or violates the rules and +protocols for communication across the network. + + Corresponding Source conveyed, and Installation Information provided, +in accord with this section must be in a format that is publicly +documented (and with an implementation available to the public in +source code form), and must require no special password or key for +unpacking, reading or copying. + + 7. Additional Terms. + + "Additional permissions" are terms that supplement the terms of this +License by making exceptions from one or more of its conditions. +Additional permissions that are applicable to the entire Program shall +be treated as though they were included in this License, to the extent +that they are valid under applicable law. If additional permissions +apply only to part of the Program, that part may be used separately +under those permissions, but the entire Program remains governed by +this License without regard to the additional permissions. + + When you convey a copy of a covered work, you may at your option +remove any additional permissions from that copy, or from any part of +it. (Additional permissions may be written to require their own +removal in certain cases when you modify the work.) You may place +additional permissions on material, added by you to a covered work, +for which you have or can give appropriate copyright permission. + + Notwithstanding any other provision of this License, for material you +add to a covered work, you may (if authorized by the copyright holders of +that material) supplement the terms of this License with terms: + + a) Disclaiming warranty or limiting liability differently from the + terms of sections 15 and 16 of this License; or + + b) Requiring preservation of specified reasonable legal notices or + author attributions in that material or in the Appropriate Legal + Notices displayed by works containing it; or + + c) Prohibiting misrepresentation of the origin of that material, or + requiring that modified versions of such material be marked in + reasonable ways as different from the original version; or + + d) Limiting the use for publicity purposes of names of licensors or + authors of the material; or + + e) Declining to grant rights under trademark law for use of some + trade names, trademarks, or service marks; or + + f) Requiring indemnification of licensors and authors of that + material by anyone who conveys the material (or modified versions of + it) with contractual assumptions of liability to the recipient, for + any liability that these contractual assumptions directly impose on + those licensors and authors. + + All other non-permissive additional terms are considered "further +restrictions" within the meaning of section 10. If the Program as you +received it, or any part of it, contains a notice stating that it is +governed by this License along with a term that is a further +restriction, you may remove that term. If a license document contains +a further restriction but permits relicensing or conveying under this +License, you may add to a covered work material governed by the terms +of that license document, provided that the further restriction does +not survive such relicensing or conveying. + + If you add terms to a covered work in accord with this section, you +must place, in the relevant source files, a statement of the +additional terms that apply to those files, or a notice indicating +where to find the applicable terms. + + Additional terms, permissive or non-permissive, may be stated in the +form of a separately written license, or stated as exceptions; +the above requirements apply either way. + + 8. Termination. + + You may not propagate or modify a covered work except as expressly +provided under this License. Any attempt otherwise to propagate or +modify it is void, and will automatically terminate your rights under +this License (including any patent licenses granted under the third +paragraph of section 11). + + However, if you cease all violation of this License, then your +license from a particular copyright holder is reinstated (a) +provisionally, unless and until the copyright holder explicitly and +finally terminates your license, and (b) permanently, if the copyright +holder fails to notify you of the violation by some reasonable means +prior to 60 days after the cessation. + + Moreover, your license from a particular copyright holder is +reinstated permanently if the copyright holder notifies you of the +violation by some reasonable means, this is the first time you have +received notice of violation of this License (for any work) from that +copyright holder, and you cure the violation prior to 30 days after +your receipt of the notice. + + Termination of your rights under this section does not terminate the +licenses of parties who have received copies or rights from you under +this License. If your rights have been terminated and not permanently +reinstated, you do not qualify to receive new licenses for the same +material under section 10. + + 9. Acceptance Not Required for Having Copies. + + You are not required to accept this License in order to receive or +run a copy of the Program. Ancillary propagation of a covered work +occurring solely as a consequence of using peer-to-peer transmission +to receive a copy likewise does not require acceptance. However, +nothing other than this License grants you permission to propagate or +modify any covered work. These actions infringe copyright if you do +not accept this License. Therefore, by modifying or propagating a +covered work, you indicate your acceptance of this License to do so. + + 10. Automatic Licensing of Downstream Recipients. + + Each time you convey a covered work, the recipient automatically +receives a license from the original licensors, to run, modify and +propagate that work, subject to this License. You are not responsible +for enforcing compliance by third parties with this License. + + An "entity transaction" is a transaction transferring control of an +organization, or substantially all assets of one, or subdividing an +organization, or merging organizations. If propagation of a covered +work results from an entity transaction, each party to that +transaction who receives a copy of the work also receives whatever +licenses to the work the party's predecessor in interest had or could +give under the previous paragraph, plus a right to possession of the +Corresponding Source of the work from the predecessor in interest, if +the predecessor has it or can get it with reasonable efforts. + + You may not impose any further restrictions on the exercise of the +rights granted or affirmed under this License. For example, you may +not impose a license fee, royalty, or other charge for exercise of +rights granted under this License, and you may not initiate litigation +(including a cross-claim or counterclaim in a lawsuit) alleging that +any patent claim is infringed by making, using, selling, offering for +sale, or importing the Program or any portion of it. + + 11. Patents. + + A "contributor" is a copyright holder who authorizes use under this +License of the Program or a work on which the Program is based. The +work thus licensed is called the contributor's "contributor version". + + A contributor's "essential patent claims" are all patent claims +owned or controlled by the contributor, whether already acquired or +hereafter acquired, that would be infringed by some manner, permitted +by this License, of making, using, or selling its contributor version, +but do not include claims that would be infringed only as a +consequence of further modification of the contributor version. For +purposes of this definition, "control" includes the right to grant +patent sublicenses in a manner consistent with the requirements of +this License. + + Each contributor grants you a non-exclusive, worldwide, royalty-free +patent license under the contributor's essential patent claims, to +make, use, sell, offer for sale, import and otherwise run, modify and +propagate the contents of its contributor version. + + In the following three paragraphs, a "patent license" is any express +agreement or commitment, however denominated, not to enforce a patent +(such as an express permission to practice a patent or covenant not to +sue for patent infringement). To "grant" such a patent license to a +party means to make such an agreement or commitment not to enforce a +patent against the party. + + If you convey a covered work, knowingly relying on a patent license, +and the Corresponding Source of the work is not available for anyone +to copy, free of charge and under the terms of this License, through a +publicly available network server or other readily accessible means, +then you must either (1) cause the Corresponding Source to be so +available, or (2) arrange to deprive yourself of the benefit of the +patent license for this particular work, or (3) arrange, in a manner +consistent with the requirements of this License, to extend the patent +license to downstream recipients. "Knowingly relying" means you have +actual knowledge that, but for the patent license, your conveying the +covered work in a country, or your recipient's use of the covered work +in a country, would infringe one or more identifiable patents in that +country that you have reason to believe are valid. + + If, pursuant to or in connection with a single transaction or +arrangement, you convey, or propagate by procuring conveyance of, a +covered work, and grant a patent license to some of the parties +receiving the covered work authorizing them to use, propagate, modify +or convey a specific copy of the covered work, then the patent license +you grant is automatically extended to all recipients of the covered +work and works based on it. + + A patent license is "discriminatory" if it does not include within +the scope of its coverage, prohibits the exercise of, or is +conditioned on the non-exercise of one or more of the rights that are +specifically granted under this License. You may not convey a covered +work if you are a party to an arrangement with a third party that is +in the business of distributing software, under which you make payment +to the third party based on the extent of your activity of conveying +the work, and under which the third party grants, to any of the +parties who would receive the covered work from you, a discriminatory +patent license (a) in connection with copies of the covered work +conveyed by you (or copies made from those copies), or (b) primarily +for and in connection with specific products or compilations that +contain the covered work, unless you entered into that arrangement, +or that patent license was granted, prior to 28 March 2007. + + Nothing in this License shall be construed as excluding or limiting +any implied license or other defenses to infringement that may +otherwise be available to you under applicable patent law. + + 12. No Surrender of Others' Freedom. + + If conditions are imposed on you (whether by court order, agreement or +otherwise) that contradict the conditions of this License, they do not +excuse you from the conditions of this License. If you cannot convey a +covered work so as to satisfy simultaneously your obligations under this +License and any other pertinent obligations, then as a consequence you may +not convey it at all. For example, if you agree to terms that obligate you +to collect a royalty for further conveying from those to whom you convey +the Program, the only way you could satisfy both those terms and this +License would be to refrain entirely from conveying the Program. + + 13. Remote Network Interaction; Use with the GNU General Public License. + + Notwithstanding any other provision of this License, if you modify the +Program, your modified version must prominently offer all users +interacting with it remotely through a computer network (if your version +supports such interaction) an opportunity to receive the Corresponding +Source of your version by providing access to the Corresponding Source +from a network server at no charge, through some standard or customary +means of facilitating copying of software. This Corresponding Source +shall include the Corresponding Source for any work covered by version 3 +of the GNU General Public License that is incorporated pursuant to the +following paragraph. + + Notwithstanding any other provision of this License, you have +permission to link or combine any covered work with a work licensed +under version 3 of the GNU General Public License into a single +combined work, and to convey the resulting work. The terms of this +License will continue to apply to the part which is the covered work, +but the work with which it is combined will remain governed by version +3 of the GNU General Public License. + + 14. Revised Versions of this License. + + The Free Software Foundation may publish revised and/or new versions of +the GNU Affero General Public License from time to time. Such new versions +will be similar in spirit to the present version, but may differ in detail to +address new problems or concerns. + + Each version is given a distinguishing version number. If the +Program specifies that a certain numbered version of the GNU Affero General +Public License "or any later version" applies to it, you have the +option of following the terms and conditions either of that numbered +version or of any later version published by the Free Software +Foundation. If the Program does not specify a version number of the +GNU Affero General Public License, you may choose any version ever published +by the Free Software Foundation. + + If the Program specifies that a proxy can decide which future +versions of the GNU Affero General Public License can be used, that proxy's +public statement of acceptance of a version permanently authorizes you +to choose that version for the Program. + + Later license versions may give you additional or different +permissions. However, no additional obligations are imposed on any +author or copyright holder as a result of your choosing to follow a +later version. + + 15. Disclaimer of Warranty. + + THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY +APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT +HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY +OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, +THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM +IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF +ALL NECESSARY SERVICING, REPAIR OR CORRECTION. + + 16. Limitation of Liability. + + IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING +WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS +THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY +GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE +USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF +DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD +PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), +EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF +SUCH DAMAGES. + + 17. Interpretation of Sections 15 and 16. + + If the disclaimer of warranty and limitation of liability provided +above cannot be given local legal effect according to their terms, +reviewing courts shall apply local law that most closely approximates +an absolute waiver of all civil liability in connection with the +Program, unless a warranty or assumption of liability accompanies a +copy of the Program in return for a fee. + + END OF TERMS AND CONDITIONS + + How to Apply These Terms to Your New Programs + + If you develop a new program, and you want it to be of the greatest +possible use to the public, the best way to achieve this is to make it +free software which everyone can redistribute and change under these terms. + + To do so, attach the following notices to the program. It is safest +to attach them to the start of each source file to most effectively +state the exclusion of warranty; and each file should have at least +the "copyright" line and a pointer to where the full notice is found. + + + Copyright (C) + + This program is free software: you can redistribute it and/or modify + it under the terms of the GNU Affero General Public License as published + by the Free Software Foundation, either version 3 of the License, or + (at your option) any later version. + + This program is distributed in the hope that it will be useful, + but WITHOUT ANY WARRANTY; without even the implied warranty of + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + GNU Affero General Public License for more details. + + You should have received a copy of the GNU Affero General Public License + along with this program. If not, see . + +Also add information on how to contact you by electronic and paper mail. + + If your software can interact with users remotely through a computer +network, you should also make sure that it provides a way for users to +get its source. For example, if your program is a web application, its +interface could display a "Source" link that leads users to an archive +of the code. There are many ways you could offer source, and different +solutions will be better for different programs; see section 13 for the +specific requirements. + + You should also get your employer (if you work as a programmer) or school, +if any, to sign a "copyright disclaimer" for the program, if necessary. +For more information on this, and how to apply and follow the GNU AGPL, see +. diff --git a/README.md b/README.md new file mode 100644 index 0000000..a8d674e --- /dev/null +++ b/README.md @@ -0,0 +1,137 @@ +# einherjar/contracts + +[![version](https://img.shields.io/badge/version-v1.0.0-5C4EE5?style=flat-square)](https://code.nochebuena.dev/einherjar/contracts) +[![license](https://img.shields.io/badge/license-AGPL--3.0-22863A?style=flat-square)](LICENSE) +[![go](https://img.shields.io/badge/Go-1.26+-00ADD8?style=flat-square&logo=go&logoColor=white)](https://go.dev) + +> *For those who come after.* + +The foundation of the Einherjar framework. Pure interfaces. Zero dependencies. A constitution, not a changelog. + +`contracts` defines the interfaces and minimal types that every Einherjar starter depends on. Nothing is above it in the dependency graph. Its interfaces, once published, are permanent — adding a method is a breaking change in Go, and breaking changes require a major version bump and coordinated updates across the entire framework. + +--- + +## What Is Einherjar + +In Norse mythology, the Einherjar are the chosen — warriors who fell in battle and were carried to Valhalla by the Valkyries. There they train, day after day, preparing for Ragnarök. They are not preserved for themselves. They are prepared for what comes after. + +This framework carries that name deliberately. Every interface defined here, every ADR written, every pattern documented exists for the developer who will build on this code without ever being in the room where it was designed. No tribal knowledge. No implicit conventions. The documentation is the system. + +--- + +## Module + +``` +code.nochebuena.dev/einherjar/contracts +``` + +**Dependencies:** none. This module imports only the Go standard library. +**Stability guarantee:** existing interface signatures are permanent. New interfaces may be added. Existing ones are not modified. + +--- + +## Sub-packages + +| Package | Purpose | +|---|---| +| [`lifecycle`](lifecycle/) | `Component` — three-phase managed lifecycle (OnInit → OnStart → OnStop) | +| [`observability`](observability/) | `Checkable` + `Level` — health reporting for infrastructure components | +| [`logging`](logging/) | `Logger` — structured, leveled logging | +| [`errs`](errs/) | `CodedError` + `ContextualError` — structured error enrichment consumed by the logger | +| [`security`](security/) | `Identity`, `Permission`, `PermissionMask`, `PermissionProvider` — authentication and authorization primitives | + +--- + +## Usage + +Import only the sub-packages you need. There is no root `contracts` package to import. + +```go +import ( + "code.nochebuena.dev/einherjar/contracts/lifecycle" + "code.nochebuena.dev/einherjar/contracts/logging" + "code.nochebuena.dev/einherjar/contracts/observability" + "code.nochebuena.dev/einherjar/contracts/errs" + "code.nochebuena.dev/einherjar/contracts/security" +) +``` + +### Implementing a managed component + +```go +// MyClient satisfies lifecycle.Component and observability.Checkable. +var _ lifecycle.Component = (*MyClient)(nil) +var _ observability.Checkable = (*MyClient)(nil) + +func (c *MyClient) OnInit() error { /* open connection */ } +func (c *MyClient) OnStart() error { return nil } +func (c *MyClient) OnStop() error { /* close connection */ } +func (c *MyClient) HealthCheck(ctx context.Context) error { /* ping */ } +func (c *MyClient) Name() string { return "my-client" } +func (c *MyClient) Priority() observability.Level { return observability.LevelCritical } +``` + +### Implementing structured errors + +```go +// MyErr satisfies errs.CodedError and errs.ContextualError. +var _ errs.CodedError = (*MyErr)(nil) +var _ errs.ContextualError = (*MyErr)(nil) + +func (e *MyErr) ErrorCode() string { return e.code } +func (e *MyErr) ErrorContext() map[string]any { return e.ctx } +``` + +The logger in `core` consumes these interfaces to append `error_code` and context +fields to every log record automatically — without either package importing the other. + +### Working with identity and permissions + +```go +// Store identity after authentication. +ctx = security.SetInContext(ctx, security.NewIdentity(uid, name, email)) + +// Retrieve identity downstream. +id, ok := security.FromContext(ctx) + +// Resolve and check permissions. +mask, err := provider.ResolveMask(ctx, id.UID, "orders") +if !mask.Has(PermWrite) { /* deny */ } +``` + +--- + +## Dependency Rules + +`contracts` sits at the root of the Einherjar dependency graph: + +``` +contracts + └── core (absorbs launcher, logz, xerrors, valid) + ├── web (absorbs httpserver, httpmw, httputil, health) + │ └── auth + │ ├── auth-jwt + │ └── auth-firebase + └── db-*, cache-*, storage-*, telemetry, worker, httpclient +``` + +**Changes flow outward from `contracts`, never inward.** A starter never drives a +contracts change. Before any modification, calculate the blast radius: which interfaces +are affected → which starters implement them → which starters consume those starters. +Release sequence is always contracts first, then implementors, then consumers. + +--- + +## Compliance + +```bash +go build ./... # zero external dependencies +go vet ./... +go test ./... # structural (one type per file) + behavioural tests +gofmt -l . # no output +``` + +--- + +*The Einherjar did not train for themselves. They trained for Ragnarök — for the battle they knew was coming, for those who would need them to be ready. Write code the same way.* diff --git a/compliance_test.go b/compliance_test.go new file mode 100644 index 0000000..67b98e4 --- /dev/null +++ b/compliance_test.go @@ -0,0 +1,301 @@ +package contracts_test + +import ( + "context" + "go/ast" + "go/parser" + "go/token" + "os" + "path/filepath" + "strings" + "testing" + + "code.nochebuena.dev/einherjar/contracts/observability" + "code.nochebuena.dev/einherjar/contracts/security" +) + +// TestOneExportPerFile asserts that every non-doc, non-test .go source file in the +// contracts module exports exactly one top-level declaration. This mechanically +// enforces CT-6: one file per interface or type. +func TestOneExportPerFile(t *testing.T) { + t.Parallel() + + root := "." + fset := token.NewFileSet() + + err := filepath.Walk(root, func(path string, info os.FileInfo, err error) error { + if err != nil { + return err + } + if info.IsDir() && info.Name() == ".git" { + return filepath.SkipDir + } + if !strings.HasSuffix(path, ".go") { + return nil + } + if strings.HasSuffix(path, "_test.go") { + return nil + } + if filepath.Base(path) == "doc.go" { + return nil + } + + f, parseErr := parser.ParseFile(fset, path, nil, 0) + if parseErr != nil { + t.Errorf("parse error in %s: %v", path, parseErr) + return nil + } + + count := countExportedTypes(f) + if count != 1 { + t.Errorf("%s: want exactly 1 exported type declaration, got %d", path, count) + } + return nil + }) + if err != nil { + t.Fatalf("walk error: %v", err) + } +} + +// countExportedTypes counts top-level exported type declarations in a parsed file. +// Constants, variables, and functions are not counted — they are part of a type's +// API and may coexist with it in the same file. CT-6 requires one type per file, +// not one symbol per file. +func countExportedTypes(f *ast.File) int { + count := 0 + for _, decl := range f.Decls { + if gd, ok := decl.(*ast.GenDecl); ok { + for _, spec := range gd.Specs { + if ts, ok := spec.(*ast.TypeSpec); ok && ast.IsExported(ts.Name.Name) { + count++ + } + } + } + } + return count +} + +// TestIdentityIsValueType verifies that Identity.WithTenant returns a new value +// without mutating the receiver. +func TestIdentityIsValueType(t *testing.T) { + t.Parallel() + + original := security.NewIdentity("uid-1", "Alice", "alice@example.com") + enriched := original.WithTenant("tenant-abc") + + if original.TenantID != "" { + t.Errorf("WithTenant mutated receiver: original.TenantID = %q, want empty", original.TenantID) + } + if enriched.TenantID != "tenant-abc" { + t.Errorf("WithTenant: enriched.TenantID = %q, want %q", enriched.TenantID, "tenant-abc") + } + if enriched.UID != original.UID { + t.Errorf("WithTenant: enriched.UID = %q, want %q", enriched.UID, original.UID) + } +} + +// TestIdentityContextRoundtrip verifies SetInContext and FromContext. +func TestIdentityContextRoundtrip(t *testing.T) { + t.Parallel() + + id := security.NewIdentity("uid-2", "Bob", "bob@example.com") + ctx := security.SetInContext(context.Background(), id) + + got, ok := security.FromContext(ctx) + if !ok { + t.Fatal("FromContext: want ok=true, got false") + } + if got != id { + t.Errorf("FromContext: got %+v, want %+v", got, id) + } +} + +// TestFromContextMissing verifies FromContext returns zero value and false on an +// empty context. +func TestFromContextMissing(t *testing.T) { + t.Parallel() + + got, ok := security.FromContext(context.Background()) + if ok { + t.Error("FromContext on empty context: want ok=false, got true") + } + if got != (security.Identity{}) { + t.Errorf("FromContext on empty context: got %+v, want zero value", got) + } +} + +// TestPermissionMaskRoundtrip verifies Grant and Has. +func TestPermissionMaskRoundtrip(t *testing.T) { + t.Parallel() + + const read security.Permission = 0 + const write security.Permission = 1 + const del security.Permission = 2 + + mask := security.PermissionMask(0).Grant(read).Grant(write) + + if !mask.Has(read) { + t.Error("Has(read): want true, got false") + } + if !mask.Has(write) { + t.Error("Has(write): want true, got false") + } + if mask.Has(del) { + t.Error("Has(del): want false, got true") + } +} + +// TestPermissionMaskBoundaries verifies out-of-range positions are rejected. +func TestPermissionMaskBoundaries(t *testing.T) { + t.Parallel() + + full := security.PermissionMask(^int64(0)) + + if full.Has(-1) { + t.Error("Has(-1): want false, got true") + } + if full.Has(63) { + t.Error("Has(63): want false, got true") + } + if full.Has(security.MaxPermission + 1) { + t.Errorf("Has(MaxPermission+1): want false, got true") + } +} + +// TestSecurityBagNewAndGet verifies construction and attribute access. +func TestSecurityBagNewAndGet(t *testing.T) { + t.Parallel() + + id := security.NewIdentity("uid-1", "Alice", "alice@example.com") + bag := security.NewSecurityBag(id) + + if bag.Identity() != id { + t.Errorf("Identity: got %+v, want %+v", bag.Identity(), id) + } + if _, ok := bag.Get("missing"); ok { + t.Error("Get on empty bag: want ok=false, got true") + } +} + +// TestSecurityBagWith verifies that With stores a value and returns a new bag. +func TestSecurityBagWith(t *testing.T) { + t.Parallel() + + id := security.NewIdentity("uid-1", "Alice", "alice@example.com") + bag := security.NewSecurityBag(id).With("hardware_id", "hw-abc") + + v, ok := bag.Get("hardware_id") + if !ok { + t.Fatal("Get: want ok=true, got false") + } + if v != "hw-abc" { + t.Errorf("Get: got %v, want hw-abc", v) + } +} + +// TestSecurityBagImmutability verifies that With does not mutate the original bag. +func TestSecurityBagImmutability(t *testing.T) { + t.Parallel() + + id := security.NewIdentity("uid-1", "Alice", "alice@example.com") + original := security.NewSecurityBag(id) + _ = original.With("key", "value") + + if _, ok := original.Get("key"); ok { + t.Error("With mutated the original bag: key should be absent in original") + } +} + +// TestSecurityBagWithIdentity verifies WithIdentity replaces the Identity. +func TestSecurityBagWithIdentity(t *testing.T) { + t.Parallel() + + id1 := security.NewIdentity("uid-1", "Alice", "alice@example.com") + id2 := security.NewIdentity("uid-2", "Bob", "bob@example.com") + + bag := security.NewSecurityBag(id1).With("k", "v").WithIdentity(id2) + + if bag.Identity() != id2 { + t.Errorf("WithIdentity: got %+v, want %+v", bag.Identity(), id2) + } + v, ok := bag.Get("k") + if !ok || v != "v" { + t.Error("WithIdentity must preserve existing attributes") + } +} + +// TestBagContextRoundtrip verifies SetBagInContext and BagFromContext. +func TestBagContextRoundtrip(t *testing.T) { + t.Parallel() + + id := security.NewIdentity("uid-1", "Alice", "alice@example.com") + bag := security.NewSecurityBag(id).With("hardware_id", "hw-abc") + ctx := security.SetBagInContext(context.Background(), bag) + + got, ok := security.BagFromContext(ctx) + if !ok { + t.Fatal("BagFromContext: want ok=true, got false") + } + if got.Identity() != id { + t.Errorf("BagFromContext identity: got %+v, want %+v", got.Identity(), id) + } + v, ok := got.Get("hardware_id") + if !ok || v != "hw-abc" { + t.Errorf("BagFromContext attribute: got %v ok=%v, want hw-abc true", v, ok) + } +} + +// TestSetInContextReadableBag verifies that SetInContext stores a SecurityBag +// readable by BagFromContext (backward-compatible storage upgrade). +func TestSetInContextReadableBag(t *testing.T) { + t.Parallel() + + id := security.NewIdentity("uid-1", "Alice", "alice@example.com") + ctx := security.SetInContext(context.Background(), id) + + bag, ok := security.BagFromContext(ctx) + if !ok { + t.Fatal("BagFromContext after SetInContext: want ok=true, got false") + } + if bag.Identity() != id { + t.Errorf("BagFromContext identity: got %+v, want %+v", bag.Identity(), id) + } +} + +// TestSetBagInContextReadableIdentity verifies that SetBagInContext stores a value +// readable by FromContext (forward-compatible for existing callers). +func TestSetBagInContextReadableIdentity(t *testing.T) { + t.Parallel() + + id := security.NewIdentity("uid-1", "Alice", "alice@example.com") + bag := security.NewSecurityBag(id).With("extra", "val") + ctx := security.SetBagInContext(context.Background(), bag) + + got, ok := security.FromContext(ctx) + if !ok { + t.Fatal("FromContext after SetBagInContext: want ok=true, got false") + } + if got != id { + t.Errorf("FromContext identity: got %+v, want %+v", got, id) + } +} + +// TestBagFromContextMissing verifies BagFromContext returns false on empty context. +func TestBagFromContextMissing(t *testing.T) { + t.Parallel() + + _, ok := security.BagFromContext(context.Background()) + if ok { + t.Error("BagFromContext on empty context: want ok=false, got true") + } +} + +// TestLevelCriticalIsZeroValue verifies that the zero value of Level is LevelCritical. +func TestLevelCriticalIsZeroValue(t *testing.T) { + t.Parallel() + + var l observability.Level + if l != observability.LevelCritical { + t.Errorf("zero Level = %d, want LevelCritical (%d)", l, observability.LevelCritical) + } +} diff --git a/doc.go b/doc.go new file mode 100644 index 0000000..6f6902c --- /dev/null +++ b/doc.go @@ -0,0 +1,5 @@ +// Package contracts is the root of the Einherjar contracts module. +// All framework contracts are defined in sub-packages: +// lifecycle, observability, logging, errs, and security. +// This package contains no exported symbols. +package contracts diff --git a/docs/adr/ADR-001-errs-sub-package.md b/docs/adr/ADR-001-errs-sub-package.md new file mode 100644 index 0000000..9e0732d --- /dev/null +++ b/docs/adr/ADR-001-errs-sub-package.md @@ -0,0 +1,102 @@ +# ADR-001: errs Sub-package — Formalising the Error Enrichment Contract + +- **Date:** 2026-05-27 +- **Module:** `code.nochebuena.dev/einherjar/contracts` +- **Status:** Accepted + +## Context + +In micro-lib, `logz` and `xerrors` are decoupled through duck typing. `logz` defines +two private interfaces internally: + +```go +// inside logz — never exported +type errorWithCode interface { + ErrorCode() string +} +type errorWithContext interface { + ErrorContext() map[string]any +} +``` + +`xerrors.Err` happens to satisfy both. `logz` detects this at runtime via +`errors.As`. The contract exists — it just lives nowhere. Any type that implements +`ErrorCode() string` and `ErrorContext() map[string]any` gets the enrichment +behaviour, whether its author knew about `logz` or not. + +This works in a flat library collection where both packages are authored by the same +team. It breaks down in a framework context for two reasons: + +1. **No canonical definition.** A developer implementing a custom error type that + wants logger enrichment has no interface to implement against — they must read + `logz`'s source code to discover the implicit contract. + +2. **Impossible to mock or test cleanly.** A test that wants to verify error + enrichment behaviour cannot assert against a defined interface. It must rely on + the duck-type resolution happening implicitly. + +## Decision + +Introduce `contracts/errs` as a sub-package with two exported interfaces: + +```go +// errs/coded_error.go +type CodedError interface { + ErrorCode() string +} + +// errs/contextual_error.go +type ContextualError interface { + ErrorContext() map[string]any +} +``` + +`core/logz` imports `contracts/errs` and checks against these interfaces explicitly +instead of defining private duck-typed equivalents. `core/xerrors` declares compile-time +satisfaction: + +```go +var _ errs.CodedError = (*Err)(nil) +var _ errs.ContextualError = (*Err)(nil) +``` + +The clean separation is preserved — `logz` still does not import `xerrors`, and +`xerrors` still does not import `logz`. Both now depend on `contracts/errs`, which +has zero dependencies of its own. + +## Why Two Interfaces, Not One + +The interfaces are intentionally separate. ISP (Interface Segregation Principle) +requires that no consumer is forced to implement methods it does not use. + +An error may carry a machine-readable code without structured context fields. An +error may carry structured context fields without a machine-readable code. Forcing +both into a single `RichError` interface would require implementors to provide both +— a constraint that is not justified by the actual use cases. + +`logz` checks each independently via `errors.As`, which is exactly how the +duck-typed version already worked. The two-interface shape matches the actual +consumption pattern. + +## Why in `contracts`, Not in `core` + +`contracts` is the only module guaranteed to have zero Einherjar dependencies. If +`CodedError` and `ContextualError` lived in `core`, any module that wanted to +implement them would be forced to import `core` — pulling the launcher, logger, and +validator into its dependency graph. That violates the Separated Interface pattern +that `contracts` exists to enforce. + +## Consequences + +**Easier:** Custom error types have a clear interface to implement against. +`go doc code.nochebuena.dev/einherjar/contracts/errs` is the single authoritative +answer to "what does my error need to provide for logger enrichment to work?" +Compile-time verification replaces implicit duck-type discovery. + +**Harder:** `errs` is a sub-package that did not exist in micro-lib. Developers +migrating from micro-lib must adopt these interfaces explicitly rather than relying +on the duck-type bridge. This is a one-time migration cost with no ongoing burden. + +**New obligations:** `CodedError.ErrorCode()` and `ContextualError.ErrorContext()` +signatures are permanent from this release. They may not be changed without a major +version bump on `contracts`. diff --git a/docs/adr/ADR-002-file-per-type-naming.md b/docs/adr/ADR-002-file-per-type-naming.md new file mode 100644 index 0000000..bd3587f --- /dev/null +++ b/docs/adr/ADR-002-file-per-type-naming.md @@ -0,0 +1,78 @@ +# ADR-002: File-per-Type Naming Convention + +- **Date:** 2026-05-27 +- **Module:** `code.nochebuena.dev/einherjar/contracts` +- **Status:** Accepted + +## Context + +Framework-level ADR-004 establishes that `contracts` sub-packages contain one file +per interface or type (CT-6). It does not specify how those files are named. Without +an explicit convention, names tend to drift: `types.go`, `interfaces.go`, `models.go`, +or `common.go` — filenames that say nothing about what is inside. + +The naming problem compounds in `security`, which has five declarations across five +files. A developer looking at the directory listing needs to know immediately which +file to open. + +## Decision + +Every source file in `contracts` is named after the single type or interface it +declares, converted to lowercase and snake_cased for multi-word names. + +| Declaration | File | +|---|---| +| `Component` | `component.go` | +| `Checkable` | `checkable.go` | +| `Level` | `level.go` | +| `Logger` | `logger.go` | +| `CodedError` | `coded_error.go` | +| `ContextualError` | `contextual_error.go` | +| `Identity` | `identity.go` | +| `Permission` | `permission.go` | +| `PermissionMask` | `permission_mask.go` | +| `PermissionProvider` | `permission_provider.go` | + +`doc.go` files are the sole exception — they carry the package-level doc comment and +export nothing. + +Constants, package-level variables, and functions that are semantically part of a +type's API (constructors, context helpers, builder methods) coexist in the same file +as the type they serve. They are not counted as separate declarations for CT-6 +purposes — CT-6 governs type declarations, not every exported symbol. + +Examples: +- `level.go` declares `Level` and also defines `LevelCritical` and `LevelDegraded` +- `permission.go` declares `Permission` and also defines `MaxPermission` +- `identity.go` declares `Identity` and also defines `NewIdentity`, `WithTenant`, + `SetInContext`, and `FromContext` + +## Alternatives Considered + +**Single `types.go` per sub-package.** Rejected — a file named `types.go` provides +no information to a developer scanning a directory. They must open it to know what +is inside. + +**Interface files named `interface.go` or `contract.go`.** Rejected — same reason. +The filename should answer "what contract does this file define?" not "what kind of +file is this?" + +**Separate files for each function and constant.** Rejected — excessive fragmentation. +A constructor and the type it constructs are a single conceptual unit. Splitting them +forces a developer to open two files to understand one thing. + +## Consequences + +**Easier:** `find . -name "permission_mask.go"` returns exactly the file that defines +`PermissionMask`. A directory listing of `security/` reads as a vocabulary list for +that sub-package's domain. Code review diffs are unambiguous — a change to +`permission_provider.go` is a change to the `PermissionProvider` contract. + +**Harder:** Multi-word type names require a deliberate naming decision at the file +level. The snake_case rule eliminates ambiguity (`permission_mask.go` is the only +valid name for `PermissionMask`) but must be applied consistently across all modules. + +**New obligations:** Every Einherjar module inherits this convention. When a new type +is added to any module, its file is named after the type. This is not optional — the +compliance test enforces the one-type-per-file structural invariant, and the naming +convention is the human-readable complement to that mechanical check. diff --git a/docs/adr/index.md b/docs/adr/index.md new file mode 100644 index 0000000..cfbe610 --- /dev/null +++ b/docs/adr/index.md @@ -0,0 +1,11 @@ +# ADR Index — contracts + +Module-level architecture decisions for `code.nochebuena.dev/einherjar/contracts`. + +For framework-wide decisions see the +[Einherjar docs repository](https://code.nochebuena.dev/einherjar/docs). + +| ADR | Title | Status | +|---|---|---| +| [ADR-001](ADR-001-errs-sub-package.md) | errs Sub-package — Formalising the Error Enrichment Contract | Accepted | +| [ADR-002](ADR-002-file-per-type-naming.md) | File-per-Type Naming Convention | Accepted | diff --git a/errs/coded_error.go b/errs/coded_error.go new file mode 100644 index 0000000..80b56de --- /dev/null +++ b/errs/coded_error.go @@ -0,0 +1,12 @@ +package errs + +// CodedError is implemented by errors that expose a machine-readable error code. +// The core starter's Logger implementation consumes this interface to append +// error_code to structured log records. The core starter's xerrors implementation +// satisfies it via its ErrorCode method. +type CodedError interface { + // ErrorCode returns a machine-readable identifier for the error condition. + // Values are SCREAMING_SNAKE_CASE strings meaningful to frontend consumers + // (e.g. "USER_NOT_FOUND"). Internal errors must not carry a code. + ErrorCode() string +} diff --git a/errs/contextual_error.go b/errs/contextual_error.go new file mode 100644 index 0000000..cf88f91 --- /dev/null +++ b/errs/contextual_error.go @@ -0,0 +1,12 @@ +package errs + +// ContextualError is implemented by errors that expose structured key-value context +// fields. The core starter's Logger implementation consumes this interface to append +// context fields to structured log records. The core starter's xerrors implementation +// satisfies it via its ErrorContext method. +type ContextualError interface { + // ErrorContext returns a map of structured fields attached to this error. + // Keys are strings; values may be any type representable in a log record. + // The returned map must not be modified by the caller. + ErrorContext() map[string]any +} diff --git a/errs/doc.go b/errs/doc.go new file mode 100644 index 0000000..279f82b --- /dev/null +++ b/errs/doc.go @@ -0,0 +1,4 @@ +// Package errs defines the interfaces implemented by structured errors in the +// Einherjar framework. These interfaces replace the private duck-typed bridges +// previously used between logz and xerrors, enforcing the contract at compile time. +package errs diff --git a/go.mod b/go.mod new file mode 100644 index 0000000..96104db --- /dev/null +++ b/go.mod @@ -0,0 +1,3 @@ +module code.nochebuena.dev/einherjar/contracts + +go 1.26 diff --git a/lifecycle/component.go b/lifecycle/component.go new file mode 100644 index 0000000..a1a11b7 --- /dev/null +++ b/lifecycle/component.go @@ -0,0 +1,18 @@ +package lifecycle + +// Component is the lifecycle interface implemented by all managed infrastructure +// components. The framework calls OnInit on every registered component, then runs +// BeforeStart hooks, then calls OnStart. OnStop is called in reverse registration +// order during graceful shutdown. Returning a non-nil error from any hook aborts +// the phase and triggers shutdown. +type Component interface { + // OnInit initializes the component: open connections, allocate resources. + // Called sequentially for all components before any OnStart is invoked. + OnInit() error + // OnStart starts background services — goroutines, listeners, background loops. + // Called after all OnInit calls succeed and all BeforeStart hooks have run. + OnStart() error + // OnStop stops the component and releases all resources. + // Called in reverse registration order during graceful shutdown. + OnStop() error +} diff --git a/lifecycle/doc.go b/lifecycle/doc.go new file mode 100644 index 0000000..3a77a0a --- /dev/null +++ b/lifecycle/doc.go @@ -0,0 +1,3 @@ +// Package lifecycle defines the Component interface implemented by all managed +// infrastructure components in the Einherjar framework. +package lifecycle diff --git a/logging/doc.go b/logging/doc.go new file mode 100644 index 0000000..bf0f5b6 --- /dev/null +++ b/logging/doc.go @@ -0,0 +1,3 @@ +// Package logging defines the Logger interface for structured, leveled logging +// across the Einherjar framework. +package logging diff --git a/logging/logger.go b/logging/logger.go new file mode 100644 index 0000000..0b3f5e1 --- /dev/null +++ b/logging/logger.go @@ -0,0 +1,26 @@ +package logging + +import "context" + +// Logger is the interface for structured, leveled logging. +// All Einherjar starters accept Logger at their constructors and pass it +// to sub-components — never the concrete implementation. +// Implementations must be safe for concurrent use. +type Logger interface { + // Debug logs a message at DEBUG level. + Debug(msg string, args ...any) + // Info logs a message at INFO level. + Info(msg string, args ...any) + // Warn logs a message at WARN level. + Warn(msg string, args ...any) + // Error logs a message at ERROR level. err may be nil. + // Implementations should detect errs.CodedError and errs.ContextualError + // and append their fields automatically to the log record. + Error(msg string, err error, args ...any) + // With returns a new Logger with the given key-value attributes pre-attached + // to every subsequent log record produced by the returned logger. + With(args ...any) Logger + // WithContext returns a new Logger enriched with request-scoped fields stored + // in ctx. Safe to call with a nil context — returns the receiver unchanged. + WithContext(ctx context.Context) Logger +} diff --git a/observability/checkable.go b/observability/checkable.go new file mode 100644 index 0000000..2246932 --- /dev/null +++ b/observability/checkable.go @@ -0,0 +1,17 @@ +package observability + +import "context" + +// Checkable is the interface implemented by infrastructure components that report +// their health status to a health handler. Pass Checkable components to the web +// starter's health handler — the handler calls each concurrently with a deadline. +type Checkable interface { + // HealthCheck performs a connectivity or liveness probe for the component. + // Returns nil when the component is healthy, a non-nil error otherwise. + // Implementations must respect ctx cancellation and return promptly on timeout. + HealthCheck(ctx context.Context) error + // Name returns the component's display name used in health check responses. + Name() string + // Priority returns the criticality level of this component. + Priority() Level +} diff --git a/observability/doc.go b/observability/doc.go new file mode 100644 index 0000000..c22f66a --- /dev/null +++ b/observability/doc.go @@ -0,0 +1,3 @@ +// Package observability defines the Checkable interface for infrastructure health +// reporting and the Level type that classifies component criticality. +package observability diff --git a/observability/identifiable.go b/observability/identifiable.go new file mode 100644 index 0000000..351b001 --- /dev/null +++ b/observability/identifiable.go @@ -0,0 +1,14 @@ +package observability + +// Identifiable is implemented by infrastructure components that can report their +// module identity — the import path and released version. +// The launcher reads this interface from all registered components to print +// the loaded-module list after the startup banner. +type Identifiable interface { + // ModulePath returns the fully-qualified Go module import path. + // Example: "code.nochebuena.dev/einherjar/web" + ModulePath() string + // ModuleVersion returns the version this module was compiled at. + // Returns "(devel)" when the binary was built from a local workspace. + ModuleVersion() string +} diff --git a/observability/level.go b/observability/level.go new file mode 100644 index 0000000..03ebde0 --- /dev/null +++ b/observability/level.go @@ -0,0 +1,15 @@ +package observability + +// Level classifies the criticality of a component to the overall application health. +// The zero value is LevelCritical — a safe default that treats unknown components +// as essential. +type Level int + +const ( + // LevelCritical marks a component essential for application function. + // A failing critical component sets the overall health status to DOWN (HTTP 503). + LevelCritical Level = iota + // LevelDegraded marks a component that is important but not essential. + // A failing degraded component sets the overall status to DEGRADED (HTTP 200). + LevelDegraded +) diff --git a/security/doc.go b/security/doc.go new file mode 100644 index 0000000..3282f98 --- /dev/null +++ b/security/doc.go @@ -0,0 +1,4 @@ +// Package security defines the Identity type representing an authenticated +// principal, the PermissionProvider interface for resolving access masks, and +// the Permission and PermissionMask types for capability modelling. +package security diff --git a/security/identity.go b/security/identity.go new file mode 100644 index 0000000..a1ccc13 --- /dev/null +++ b/security/identity.go @@ -0,0 +1,75 @@ +package security + +import "context" + +// Identity represents the authenticated principal for a request. +// +// Identity is a value type — always copied, never a pointer — to prevent +// nil-check burden and accidental mutation of a shared context value. +// Construction follows a two-step pattern: NewIdentity populates authentication +// data from the token (uid, name, email); WithTenant optionally enriches with a +// tenant ID in a later middleware step, returning a new value without mutating +// the original. +type Identity struct { + UID string + TenantID string + DisplayName string + Email string +} + +// authContextKey is the unexported context key used to store Identity values. +// Using a private type prevents collisions with keys from other packages. +type authContextKey struct{} + +var authKey = authContextKey{} + +// NewIdentity creates an Identity from token authentication data. +// TenantID is left empty — populate it later with WithTenant once the enrichment +// middleware has resolved it from the request context. +func NewIdentity(uid, displayName, email string) Identity { + return Identity{ + UID: uid, + DisplayName: displayName, + Email: email, + } +} + +// WithTenant returns a copy of the Identity with TenantID set to id. +// The receiver is not mutated — safe to call from concurrent middleware. +func (i Identity) WithTenant(id string) Identity { + i.TenantID = id + return i +} + +// SetInContext stores id in ctx as a [SecurityBag] and returns the enriched context. +// Callers that need to attach additional request-level attributes should use +// [SetBagInContext] directly. [FromContext] continues to work unchanged. +func SetInContext(ctx context.Context, id Identity) context.Context { + return SetBagInContext(ctx, NewSecurityBag(id)) +} + +// FromContext retrieves the Identity stored by [SetInContext] or [SetBagInContext]. +// Returns the zero-value Identity and false if no identity is present in ctx. +func FromContext(ctx context.Context) (Identity, bool) { + bag, ok := BagFromContext(ctx) + if !ok { + return Identity{}, false + } + return bag.Identity(), true +} + +// SetBagInContext stores bag in ctx and returns the enriched context. +// Use this when you need to attach request-level attributes beyond the Identity +// (hardware IDs, grant codes, etc.) via [SecurityBag.With]. +func SetBagInContext(ctx context.Context, bag SecurityBag) context.Context { + return context.WithValue(ctx, authKey, bag) +} + +// BagFromContext retrieves the [SecurityBag] stored by [SetBagInContext] or [SetInContext]. +// Returns an empty SecurityBag and false if no bag is present in ctx. +// Permission providers use this to access both the Identity and any extra attributes +// injected during enrichment. +func BagFromContext(ctx context.Context) (SecurityBag, bool) { + bag, ok := ctx.Value(authKey).(SecurityBag) + return bag, ok +} diff --git a/security/permission.go b/security/permission.go new file mode 100644 index 0000000..0933367 --- /dev/null +++ b/security/permission.go @@ -0,0 +1,19 @@ +package security + +// Permission is a named bit position (0–62) representing a single capability. +// +// Applications define their own permission constants using this type: +// +// const ( +// Read security.Permission = 0 +// Write security.Permission = 1 +// Delete security.Permission = 2 +// ) +// +// Valid positions are 0 through MaxPermission (62). Values outside that range +// are silently ignored by PermissionMask.Has and PermissionMask.Grant. +type Permission int64 + +// MaxPermission is the highest valid bit position for a Permission constant. +// Bit 63 is reserved for the sign bit of the underlying int64. +const MaxPermission Permission = 62 diff --git a/security/permission_mask.go b/security/permission_mask.go new file mode 100644 index 0000000..99486c8 --- /dev/null +++ b/security/permission_mask.go @@ -0,0 +1,26 @@ +package security + +// PermissionMask is a resolved bit-mask for a user on a specific resource. +// It is returned by PermissionProvider.ResolveMask and inspected with Has. +// A zero value means no permissions are granted. +type PermissionMask int64 + +// Has reports whether the given permission bit is set in the mask. +// Returns false for out-of-range values (p < 0 or p > MaxPermission). +func (m PermissionMask) Has(p Permission) bool { + if p < 0 || p >= 63 { + return false + } + return (int64(m) & (1 << uint(p))) != 0 +} + +// Grant returns a new mask with the bit for p set. +// The receiver is not modified — safe to use in builder chains: +// +// mask := security.PermissionMask(0).Grant(Read).Grant(Write) +func (m PermissionMask) Grant(p Permission) PermissionMask { + if p < 0 || p >= 63 { + return m + } + return PermissionMask(int64(m) | (1 << uint(p))) +} diff --git a/security/permission_provider.go b/security/permission_provider.go new file mode 100644 index 0000000..46fdace --- /dev/null +++ b/security/permission_provider.go @@ -0,0 +1,18 @@ +package security + +import "context" + +// PermissionProvider resolves the permission mask for a user on a given resource. +// +// Implementations may call FromContext to retrieve the Identity (and its TenantID) +// when multi-tenancy is required — there is no need to thread tenantID as an +// explicit parameter since it is already in the context. +// +// The resource string identifies what is being accessed (e.g. "orders", +// "invoices"). Its meaning is defined by the application domain. +type PermissionProvider interface { + // ResolveMask returns the PermissionMask for uid on resource. + // A zero mask means no permissions are granted. Callers check individual + // bits with PermissionMask.Has using domain-defined Permission constants. + ResolveMask(ctx context.Context, uid, resource string) (PermissionMask, error) +} diff --git a/security/security_bag.go b/security/security_bag.go new file mode 100644 index 0000000..6b141a2 --- /dev/null +++ b/security/security_bag.go @@ -0,0 +1,55 @@ +package security + +// SecurityBag is the request-scoped security context for a single request. +// It carries the authenticated [Identity] alongside any additional attributes +// injected during the enrichment phase (hardware IDs, grant codes, etc.). +// +// SecurityBag is a value type — all mutation methods return a new value without +// modifying the receiver. The attribute map is copied on every [SecurityBag.With] +// call to preserve this guarantee. +// +// The framework defines no string key constants for bag attributes — all +// framework-known fields live as typed fields on [Identity]. Callers define +// their own constants to avoid collisions: +// +// const KeyHardwareID = "hardware_id" +// +// bag.With(KeyHardwareID, hwID) +// val, ok := bag.Get(KeyHardwareID) +type SecurityBag struct { + identity Identity + attributes map[string]any +} + +// NewSecurityBag creates a SecurityBag wrapping id with an empty attribute map. +func NewSecurityBag(id Identity) SecurityBag { + return SecurityBag{identity: id} +} + +// Identity returns the authenticated Identity stored in the bag. +func (b SecurityBag) Identity() Identity { + return b.identity +} + +// WithIdentity returns a copy of the bag with the Identity replaced by id. +// Used by bag enrichers that modify the Identity (e.g., [authmw.WithTenantHeader]). +func (b SecurityBag) WithIdentity(id Identity) SecurityBag { + return SecurityBag{identity: id, attributes: b.attributes} +} + +// Get returns the attribute stored under key and true, or (nil, false) if absent. +func (b SecurityBag) Get(key string) (any, bool) { + v, ok := b.attributes[key] + return v, ok +} + +// With returns a copy of the bag with key set to value. +// The receiver is not modified — safe to call from concurrent middleware chains. +func (b SecurityBag) With(key string, value any) SecurityBag { + attrs := make(map[string]any, len(b.attributes)+1) + for k, v := range b.attributes { + attrs[k] = v + } + attrs[key] = value + return SecurityBag{identity: b.identity, attributes: attrs} +}