Signal Architecture
A way of placing App Analytics in a product: what must be true of events, identity, and consent before anyone argues about a chart.
Three layers we draw on the wall
Capture — the client or server emits a named action. Identity — a person is attached only as far as you can defend. Meaning — a funnel or cohort is allowed to exist because the names underneath it are frozen.
Most teams reverse the order. They buy a dashboard, then hunt for events to feed it. Signal Architecture forbids that sequence in our rooms.
Where it shows up in teaching
Event Taxonomy Studio is the capture layer. Retention Literacy and Funnel Instrumentation sit on meaning. Consent-Aware Streams cuts across identity. If you want the map before you pick a programme, this page is the map.
A working sketch, not a framework brand
We do not sell a canvas pack. The sketch is four boxes: event, property, identity, lawful basis. House Cohorts fill them on a whiteboard in Cranage until the arguments are boring. Boring dictionaries are the point.
Bring a collision list