This is a public, read-only report. Striff reads this repository's docs, turns each sentence that makes a claim about the code into a rule, and checks the rule against the code on the default branch. How this works
its registration, in priority order, where ImportCommand builds the ParserRegistry
ImportCommand depends on ParserRegistry
HoldsVandox.Backend → Vandox.Core
the log import framework and the log signature catalog with its detector (Vandox.Core.Signatures; vandoxd incidents uses it, the running service does not apply it to live data yet), the log templates with their statistics and queries (Vandox.Core.Templates, Vandox.Storage), the overview page of the web UI (/: freshness, services, key figures, incidents; Vandox.Backend),
2 rules from this sentence
something in Vandox.Backend.Cli depends on something in Vandox.Core.Signatures
checks “the log import framework and the log signature catalog with its detector (Vandox.Core.Signatures; vandoxd incidents uses it, the running service does not apply it to live data yet), the log templates with their statistics and queries (Vandox.Core.Templates, Vandox.Storage), the overview page of the web UI (/:”
HoldsBackend → Core
OverviewPage is in Vandox.Backend
checks “the overview page”
Holds
the incidents view of the web UI (list, incident page with charts of the window, notes; Vandox.Backend) exist (vandoxd import, with the parsers for the journal export, the MariaDB error log, Dovecot's own log file, syslog and kern.log, the Plesk panel log, the nginx, sw-cp-server and Apache error logs and the legacy top/lsof monitoring log): vandoxd loads its configuration, opens and migrates its SQLite database (schema, batched writes, queries and log search exist as the storage layer; the service reads it through the overview page, the history, logs and incidents views and the report page with its download and writes the notes of incidents and the agent's batches, vandoxd import writes through it),
3 rules from this sentence
something in Vandox.Backend.Cli depends on something in Vandox.Core.LogParsing
checks “vandoxd import, with the parsers”
HoldsBackend → Core
ReportPage is in Vandox.Backend
Holds
IncidentsView is in Vandox.Backend
checks “the incidents view”
Holds
vandoxd loads its configuration, opens and migrates its SQLite database (schema, batched writes, queries and log search exist as the storage layer; the service reads it through the overview page, the history, logs and incidents views and the report page with its download and writes the notes of incidents and the agent's batches, vandoxd import writes through it),
2 rules from this sentence
OverviewPage depends on something in Vandox.Storage
checks “the service reads it through the overview page”
Holdssrc → Vandox
something in Vandox.Backend.Cli depends on something in Vandox.Storage
checks “vandoxd import writes through it”
HoldsBackend → Storage
the log import framework and the log signature catalog with its detector (Vandox.Core.Signatures; vandoxd incidents uses it, the running service does not apply it to live data yet), the log templates with their statistics and queries (Vandox.Core.Templates, Vandox.Storage), the overview page of the web UI (/: freshness, services, key figures, incidents; Vandox.Backend), the logs view of the web UI (search, context, template list and chart; Vandox.Backend), the history view of the web UI (chosen metrics over a range in one chart, events and the snapshots of a moment; Vandox.Backend), the outage reconstruction (vandoxd incidents, Vandox.Core.Incidents),
2 rules from this sentence
HistoryView depends on something in Vandox.Storage
Holdssrc → Vandox
LogsView depends on something in Vandox.Storage
Holdssrc → Vandox
the logs view of the web UI (search, context, template list and chart; Vandox.Backend), the history view of the web UI (chosen metrics over a range in one chart, events and the snapshots of a moment; Vandox.Backend), the outage reconstruction (vandoxd incidents, Vandox.Core.Incidents),
2 rules from this sentence
LogsView is in Vandox.Backend
Holds
HistoryView is in Vandox.Backend
checks “the history view”
Holds
listens on the web and ingest ports, accepts the agent's batches on its ingest endpoint (POST /v1/batches: the token bound to one configured agent ID, bounded body, batch and time, two slots through the commit, a free-space floor; Vandox.BackendIngest),
IngestEndpoint is in Vandox.Backend.Ingest
Holds
The time-series service (TimeSeriesService over ITimeSeriesReader, behind the views' read gate) answers the views' queries for metric lines with their gaps and markers in process,
TimeSeriesService depends on ITimeSeriesReader
Holds
The logs view does not use this search directly: it searches in bounded pages, from the full-text index when the words match fewer than a cap of rows and otherwise by a time-ordered scan of at most a fixed number of lines,
LogsView may not depend on LogSearch
HoldsVandox.Backend → Vandox.Storage
internal/config (Go) for the agent and Vandox.Core.Configuration (C#) for the backend (0078).
something in src/Vandox.Backend depends on something in Vandox.Core.Configuration
Holdssrc → Vandox
Vandox.Core.Reports (ForensicsAnalysis with Seal and Summarize, ObservedHours, SnapshotSeries, ConsumerTracker, RecurrenceRules, PanelPrograms, ReportLimits, ProgramStatistics and the result types) for the analysis;
10 rules from this sentence
ForensicsAnalysis, ObservedHours, SnapshotSeries and 5 more are in Vandox.Core.Reportschecks “Vandox.Core.Reports (ForensicsAnalysis with Seal and Summarize, ObservedHours, SnapshotSeries, ConsumerTracker, RecurrenceRules, PanelPrograms, ReportLimits, ProgramStatistics and the result types)”
Holdsall 8
ForensicsAnalysis has Seal
checks “ForensicsAnalysis with Seal and Summarize”
Holds
ForensicsAnalysis has Summarize
checks “ForensicsAnalysis with Seal and Summarize”
Holds
Vandox.Backend (Reports/ForensicsReporter, Reports/IReportWriter, Reports/ReportComposer with the blocks ReportBlock, ReportBlockKind and ReportPiece, Reports/MarkdownReportWriter, Reports/MarkdownText, Reports/ReportText, Cli/ReportCommand, and Program, which opens standard output as UTF-8 without a byte order mark) for reading the store and writing the Markdown;
4 rules from this sentence
ReportCommand is in Vandox.Backend.Cli
checks “Vandox.Backend (Reports/ForensicsReporter, Reports/IReportWriter, Reports/ReportComposer with the blocks ReportBlock, ReportBlockKind and ReportPiece, Reports/MarkdownReportWriter, Reports/MarkdownText, Reports/ReportText, Cli/ReportCommand, and Program”
Holds
ReportComposer depends on ReportBlock
checks “Reports/ReportComposer with the blocks ReportBlock, ReportBlockKind and ReportPiece”
Holds
ReportComposer depends on ReportBlockKind
checks “Reports/ReportComposer with the blocks ReportBlock, ReportBlockKind and ReportPiece”
Holds
ReportComposer depends on ReportPiece
checks “Reports/ReportComposer with the blocks ReportBlock, ReportBlockKind and ReportPiece”
Holds
timeline texts capped at 512 characters, every other field at 2,048, each text in at most 16 runs (IncidentsView.MaxTextRuns), the rest as one run (0207).
IncidentsView has MaxTextRuns
Holds
Incidents/ (IncidentsView, IncidentRowView, IncidentDetailView, IncidentWindowReader, ProgramMemorySeries, GatedIncidentBrowser, GatedRecordReader, IncidentNoteText, IncidentNoteEndpoint with RequiredAntiforgery and no AllowAnonymous, logging IncidentNoteSaveFailed);
IncidentNoteEndpoint depends on RequiredAntiforgery
HoldsIncidents → Security
Vandox.Backend: Components/Pages/ReportPage, Components/Reports/ReportContent (external text as <code><ExternalText Runs="…" /></code> with LogText.Runs(text, LogText.MaxShortChars), pieces as ReportPiece.Code);
7 rules from this sentence
ReportContent depends on ExternalText
checks “Components/Pages/ReportPage, Components/Reports/ReportContent (external text as <code><ExternalText Runs="…" /></code> with LogText.Runs(text, LogText.MaxShortChars), pieces as ReportPiece.Code);”
HoldsReports → Logs
ReportContent depends on LogText
checks “Components/Pages/ReportPage, Components/Reports/ReportContent (external text as <code><ExternalText Runs="…" /></code> with LogText.Runs(text, LogText.MaxShortChars), pieces as ReportPiece.Code);”
Reports/ (ReportService with the run slot, ReportsView with Deadline, PageHref, DownloadHref and FileName, ReportViewBuilder, ReportDocument, ReportAddress with Parse and ToQuery, ReportDownloadEndpoint, GatedIncidentStore whose SaveIncidentAsync refuses, GatedListenerHistoryReader, and the blocks ReportComposer, ReportBlock, ReportPiece);
7 rules from this sentence
ReportsView has Deadline
checks “ReportsView with Deadline, PageHref, DownloadHref and FileName”
Holds
ReportsView has PageHref
checks “ReportsView with Deadline, PageHref, DownloadHref and FileName”
Holds
ReportsView has DownloadHref
checks “ReportsView with Deadline, PageHref, DownloadHref and FileName”
Holds
ReportsView has FileName
checks “ReportsView with Deadline, PageHref, DownloadHref and FileName”
the uncancellable steps are ForensicsAnalysis.Seal and Summarize;
ForensicsAnalysis has Seal
Holds
the range is defined once in Vandox.Core (StorableTime) and storage uses the same definition.
StorableTime is in Vandox.Core
Holds
The rule lives in the shared PayloadRegistry.Options, so the storage read path (RecordQueries.ReadJson) applies it too. That changes nothing for the rows the store writes, which are validated and serialized without null members; a null in a hand-edited stored payload reads as an empty value instead of a null reference.
2 rules from this sentence
RecordQueries depends on PayloadRegistry
checks “The rule lives in the shared PayloadRegistry.Options, so the storage read path (RecordQueries.ReadJson) applies it too.”
HoldsVandox.Storage → Vandox.Core
PayloadRegistry has Options
checks “The rule lives in the shared PayloadRegistry.Options”