📖What it means

WHERE an initiative filing came from - the fact that decides its execution lane. The ruled sources: a redirect; an Albus escalation (off his bypass track or off the planner escalation track); an operator request (Ninad via the CLI); the Carolverse ADMIN filing from one of Orion's own chat windows; a filing made during an Orion bypass execution; a filing from chat by a user; a chat filing where the person EXPLICITLY asked for the planner; a planner escalation; an autonomous agent filing. An explicit filing_source field on the create wins; otherwise the seam derives it from the channel and the requester, and an underivable source changes nothing.

📖Easily confused with

[{"term": "Originating channel", "distinction": "The channel is the door the request walked through; the filing source is the ruled CLASS that decides the lane."}, {"term": "Requester", "distinction": "The requester is who asked; the filing source may REASSIGN requester/owner (e.g. a mid-bypass finding becomes Albus's). It also cannot be read backwards: a chat filing names the AGENT as requester, so the requester never proves a source."}]

📖Nuance

Two of the sources cannot be derived at the seam at all, because the facts they turn on - which chat WINDOW this is, and whether the person is the admin - exist only at the door, as trusted turn context. Those two are DECLARED by the door and never guessed. Everything the seam does derive it derives from the CHANNEL first: a chat-like channel is a user chat whatever the requester says.

📖Also called

- source of filing
- filing origin

📖Filed under

Category: work.

Service: Build Initiatives.