davidfacer.com / aimaturitymodels.com / Vellum & Seminum

Vellum & Seminum

Two tools built on top of EA OKF, for two different problems: seeing a corpus, and seeding one. They began as a matched pair of internal tools and have since diverged — Vellum stays closed working tooling, Seminum is on its way to being a product. Described here so their absence from the rest of this site doesn’t read as an oversight.

Vellum — seeing the corpus

A governed corpus is only as useful as it is legible. Vellum is a read-only renderer that makes the corpus’s records and the relationships between them navigable at multiple altitudes — a single decision, a whole work package, or the practice’s entire governed history — without hand-authoring a one-off document for each view. The name is deliberate: pre-digital architects drafted on thin vellum sheets specifically so several layered plans could be overlaid on a light table and read in relation to each other. That’s exactly what this tool does across the corpus’s typed edges.

Seminum — seeding a new practice

Every practice built this way accumulates the same pattern layer: EA OKF itself, a maturity model shaped like the ones in this family, and the process models that hold them together. Seminum is a portable package of that pattern — sanitized of any one practice’s own instance data — meant to be dropped into a new repository so a new practice starts from something proven instead of a blank page.

Seminum is built, and it is in a closed beta with a small number of reviewers. It is not publicly available. The pattern layer it carries is currently unlicensed; a licence is intended at its first public release, and no date has been set for that.

Vellum stays closed-access by design — not because there’s anything to hide, but because a corpus browser is an internal working tool rather than a product. Seminum was described the same way here until it was reclassified as a product in waiting; what changed then was its destination, not its present state.