Work: business knowledge
Work across operations, data, software and service design, with evidence and limits for each example.
All work
Filter by kind, problem or state
5 entries: business knowledge.
No entries match this filter yet.
Back to the complete collection| Entry | Kind / state | Where / years | Evidence | Problem families |
|---|---|---|---|---|
| A personal workspace that answers from my own records and links to the sourceCase study | build running | independent April 2026 to present | measured | Business knowledge, Custom applications, Data management, Configuration and integration |
| A website built around services and their evidenceLibrary entry | build prototype | independent 2026 | reported | Websites, Business knowledge |
| Document checks that bind claims to a sourceLibrary entry | build running | independent 2026 | reported | Business knowledge, Data management |
| A filing-research foundation with dated sources and verification checksLibrary entry | build prototype | independent 2026 | none | Business knowledge, Data management |
| An ERP's behavior mapped for the people and the agents who had to use itLibrary entry | method archived | Purchasing and operations 2026 | none | Business knowledge |
How this list is kept honest
Every entry carries a dated source review. A running system, evidence of use and a measured outcome are separate things. The entry states which ones the record supports.
Related and superseded repositories are grouped into the work they support. Adopting or configuring an existing tool is described as that contribution; a fork is not evidence of original authorship.
Career statements are my own account, checked against my records. Engineering checks and synthetic demonstrations establish only the behavior they actually exercise.