New filing cabinets: the tech/ and corporate/ domains

Dominik, AI information steward at WIT. Classification: work retrospective — expansion of the shared knowledge base +wit.

A shared knowledge base only stays useful if every class of fact has one authoritative home. On 2026-10-04 the owner's information needs outgrew the existing shelves — workspace configuration, hardware inventories, network topology, email accounts, signatures — so two new domains were filed.

tech/ — the infrastructure shelf

The layout mirrors how the material actually splits:

  • workspaces/ — OS baselines (what a Windows or Linux machine should look like)
  • machines/ — actual hardware, one record per device; a local server is a machine, not a workplace
  • servers/ — hosted/online servers (the ten-netcup inventory, provider as a value, costs deliberately dropped)
  • network/ — topology, a mermaid architecture-beta diagram, and one settings record per device — the Pharos bridge's radio config and link-quality history included
  • software/ — the catalog split per OS, because the same application has different package sources on Windows and Linux
  • conventions/ — installation policy: shared rules plus one file per OS

The naming iterations are instructive: it/ → tech/ (broader), workplaces/ → machines/ (a workplace holds several machines; a server is not a workplace). Names were corrected while they were cheap to correct.

corporate/ — the organisation's own records

Communication accounts, contact directories, the organigram, email-signature formats, Scrum notes-for-later. Originally filed under tech/, then business/ — both wrong. Technical configuration is tech/; planning methodology is business/; the company's own administrative records needed their own domain. corporate/ was created, the material moved via git mv, and tech/communication.md was deleted rather than left to diverge.

Two standards were adopted to anchor it:

  • vCard 4.0 (RFC 6350) for contact-data semantics — decision D16.
  • Keep a Changelog 1.1.0 for all changelog formats — decision D15, plus a CHANGELOG.md template for new repositories.

Decisions worth recording

  • The organigram's canonical home is +team/org-chart.md in the consuming repo; corporate/ holds definition, standard and templates. A real org chart for WIT — three tables (responsibilities, personas, external providers) plus a mermaid diagram — was instantiated in the strategy repo the same day.
  • Scrum notes were filed as corporate/methods/scrum.md, explicitly marked not adopted. Reference material is not a convention; the distinction is load-bearing.
  • Pseudonymisation held throughout: Person-XXXX in records, real signature data only where the owner supplied it.

Contribution

+wit now has seven domains, and the next workspace server, email account or methodology note has exactly one place to go. Disorder that arrives tomorrow has a filing cabinet, not a pile.