solid-pod-rs 0.5.0-alpha.21

Rust-native Solid Pod server library — LDP, WAC, WebID, Solid-OIDC, Solid Notifications, NIP-98. Framework-agnostic.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35

---
id: ADR-NNNN
title: Short imperative title
date: YYYY-MM-DD
decision_status: proposed        # proposed | accepted | rejected | superseded
implementation_status: none      # none | partial | complete
activation_status: inactive      # inactive | staged | live
supersedes: []                   # e.g. [ADR-0042]
superseded_by: []                # e.g. [ADR-2050]
verified_commit:                 # git sha at which implementation_status was verified
owner:                           # accountable person/handle
review_trigger:                  # the event/date that forces a re-review of this ADR
repo: solid-pod-rs               # solid-pod-rs
evidence_class:                  # required when implementation_status becomes complete or activation_status becomes live (adr-ratchet, VisionFlow ADR-2007): source | test | ci | deployment | runtime (join with +)
acceptance_boundary:             # required with evidence_class: what the evidence does and does not establish
---

# ADR-NNNN — Short imperative title

## Context
<!-- Max 10 lines. The forces at play: the problem, constraints, prior state.
     State facts, not narrative. If it needs more than 10 lines, it is two ADRs. -->

## Decision
<!-- The meat. What we are doing, stated in the present tense as policy.
     Be specific enough that a reader can tell whether a given change complies. -->

## Consequences
<!-- What becomes true, easier, harder, or forbidden as a result.
     Include the costs and the follow-on work, not just the upside. -->

## Verification
<!-- How implementation_status above was established: the command, test, grep,
     or artefact inspected, and at which verified_commit. This is the evidence
     that the ADR describes reality rather than intent. -->