Seryvon development notes and change evidence
These development notes explain the implementation areas visible in Seryvon's public source. They are not a fabricated release history: the v1.0.0rc4 release is now publicly tagged; hosted rollout claims are still excluded. The managed product remains coming soon; the v1.0.0rc4 open-core release is public.
From collection to an explainable report
The open core connects website discovery and crawling to signal extraction, rule evaluation and report generation. The early README milestones describe the original crawler and SEO scorecard, the additional visibility pillars, citation tracking and measurement profiles. Use those milestones as development context; consult source files for the behaviour of your chosen revision.
Persistence and comparison are present in code
The storage package provides in-memory and S3-compatible artifact stores. The comparison engine classifies measurement profiles before producing comparable score differences. Both implementations now exist, even though the README's early “next” list still mentions artifact storage and scorecard comparison.
This distinction matters when planning an evaluation. Persistent artifact storage needs configuration, and a comparison must account for differences in coverage, rules and thresholds. Neither capability should be assessed solely from a checkbox on a roadmap. Read the methodology for interpretation and the status page for deployment dependencies.
Application and operational components
The repository includes a FastAPI application, React web interface and Celery workers defined in Docker Compose. API key enforcement and encrypted stored-key helpers are also present. These components provide a basis for self-hosted evaluation; they do not announce a managed launch or replace an operator's deployment review.
Review an upgrade with evidence
- Record the revision currently deployed and the revision you intend to install.
- Read the commits affecting scoring, connectors, migrations and configuration.
- Preserve your database and required artifacts before applying changes.
- Run a known target with a recorded configuration and inspect errors and coverage.
- Check measurement-profile compatibility before interpreting a score difference as website progress.
Follow repository commits for source changes and published releases for any release notes provided by maintainers. The repository currently exposes the v1.0.0rc4 tag; GitHub has published the release notes and downloadable assets, and a commit does not by itself establish production readiness.
Evidence for this overview: storage adapters, comparison engine and service configuration. Start a local evaluation with the quickstart.