Audit history and reporting
Answering 'who changed this and who agreed?' from data.
By the OneEnv team · Last updated
Four views of what happened
- Branches (merged filter): a merged branch with its changes is the permanent version record.
- History: an append-only event feed (branch created, submitted, decided, merged, reverted; impacts approved, rejected, resynced; overrides published) with filters by service, actor, type and date, and free-text search.
- Report: aggregate tabs for overview, services, environment, database, APIs, validations, errors, branches and activity, a weighted health score, and health checks.
- Dependency Graph: a read-only graph of how services, routes, tables and rules relate, with cycle detection on API source chains.
Health checks
Seven checks list concrete problems: duplicate variables that differ only by case, unused variables, orphan databases, broken references to archived items, invalid inheritance, circular dependencies, and required template values still empty.
Visibility
Members only see events, graph nodes and report rows for services they can view.
Limitations
- Impact analysis is one hop at merge time; the graph pages are views, not inputs to merge decisions.
Related