a requirements specification is a schema with a purpose column. when you write that a community organisation must receive an obsidian vault at zero cost, you are stating a constraint — not a feature — and that constraint propagates through every table that follows: who qualifies, what gets provisioned, what gets recorded as given. the requirements management doc covers what the structure must hold; the architecture requirements specification covers what shape it must take. a foreign key pointing to a beneficiary record is a claim that someone real received something real. that is what a business requirement encodes at the lowest level: an obligation the structure is not allowed to break.
full docs: requirements management https://cloud.nzrtnetwork.com/nextcloud/index.php/s/fW3RJxALi2Pp7Jq | architecture requirements specification https://cloud.nzrtnetwork.com/nextcloud/index.php/s/AFjkcy8WBrAoA7z
