tegwick
06be56fdff
The renderer and its stylesheet moved in from the-custodian with a make build target, so T02 generalises something that works rather than starting from scratch. Publication tooling belongs to the repo that owns publication. Disclosure is resolved for now: full public is fine in build mode, where there are no users to expose and no attacker with anything to gain. Recorded as deferred rather than closed, because it stops being true at production - the same blast-radius disclosure that a consumer must read becomes a map once real tenant data exists. Controlled disclosure is deliberately not this repo's job. Publication is about permanence and currency; embargo is about severity, remediation and timing, and building it here would put risk judgement in the repo least qualified to make it. It likely wants a service of its own - a risk-nexus - with this repo as its publication surface rather than its brain. The only cost today is one line in T01: the addressing scheme must not assume every document is public from birth, so that adding an embargo state later is a new status rather than a URL migration. First publication retargeted - the framework relocated to NetKingdom canon and is now tenancy-posture_v0.1, five axes rather than five planes. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
15 lines
510 B
Makefile
15 lines
510 B
Makefile
.PHONY: build clean
|
|
|
|
# Publication targets. Source of truth is always the upstream repo; pages here
|
|
# are generated and must never be hand-edited.
|
|
SRC_NETKINGDOM ?= $(HOME)/net-kingdom
|
|
|
|
build:
|
|
mkdir -p build
|
|
python3 tools/render.py $(SRC_NETKINGDOM)/canon/standards/tenancy-posture_v0.1.md \
|
|
--output build/tenancy-posture.html \
|
|
--title "Tenancy Posture" \
|
|
--subtitle "A framework for describing, holding and improving multi-tenancy — including where we are not there yet."
|
|
|
|
clean:
|
|
rm -rf build
|