38 lines
1.3 KiB
Markdown
38 lines
1.3 KiB
Markdown
# Decision: Read-Only Schema-Preserving Viewer
|
|
|
|
**Date:** 2026-03-15
|
|
**Status:** active
|
|
|
|
## Context
|
|
|
|
A separate repository is being created to display Reanimator JSON snapshots in a simpler and more reusable way than the existing `logpile` UI.
|
|
|
|
The goal is to let other Go applications embed the viewer module and present Reanimator snapshot data without duplicating UI work.
|
|
|
|
There was an explicit requirement that the viewer must show all JSON fields and must not add new computed data.
|
|
|
|
## Decision
|
|
|
|
Reanimator Chart is defined as a small read-only web viewer for one Reanimator JSON snapshot.
|
|
|
|
It will:
|
|
|
|
- render source data as-is
|
|
- preserve unknown fields
|
|
- use simple section navigation and tables
|
|
- color-code device statuses for presentation only
|
|
|
|
It will not:
|
|
|
|
- perform collection or parsing of raw vendor logs
|
|
- run upload/API-connect/convert workflows
|
|
- compute aggregate health summaries unless they are already present in the input JSON
|
|
- become a generic analyzer product
|
|
|
|
## Consequences
|
|
|
|
- The viewer architecture must stay minimal and server-rendered by default.
|
|
- The rendering layer must be tolerant of schema evolution.
|
|
- UI code must not silently drop unexpected fields.
|
|
- `logpile` patterns for upload, convert, collectors, and job management are out of scope here.
|