Workflow
Is AppTruth continuous or on-demand?
AppTruth scans are currently on-demand: a user selects an approved repository and explicitly starts each review.
Reviewed by Uriel from AppTruth · Updated · 3 min read
Direct answer to “Is AppTruth continuous or on-demand?”
AppTruth is currently on-demand. A user chooses an approved GitHub repository and explicitly starts a scan when they want a fresh behavior review.
Key points: Is AppTruth continuous or on-demand?
- Scans do not run continuously in the background by default.
- Each accepted scan uses plan quota.
- A fresh scan is useful after a meaningful code or release change.
When should users run a scan?
On-demand scanning gives the user control over timing, repository choice, and quota. Useful moments include the completion of a new feature, a large AI-generated change, a handoff between teams, a release candidate, or an unexpected product behavior that needs explanation.
- Before a first production launch
- After changing authentication, roles, billing, or data rules
- Before accepting an agency or AI-generated implementation
- When product expectations and observed behavior appear to disagree
Does AppTruth monitor every commit?
No. The current product does not automatically scan every commit or operate as a continuous production monitor. AppTruth can reuse an unchanged source snapshot efficiently, but the user still initiates the review. GitHub CI, deployment checks, and observability tools remain responsible for continuous automation.
On-demand verification as a release gate
Teams can make an AppTruth scan part of a human release checklist: scan the candidate code, review high-impact findings and coverage boundaries, decide which differences are intended, and run the necessary runtime tests. The decision remains with the release owner.
When to use on-demand and continuous verification
| Cadence | Best trigger | Typical owner |
|---|---|---|
| AppTruth on demand | Release candidate, handoff, or major feature | Release owner |
| CI checks | Every pull request or commit | Engineering |
| Production monitoring | Continuous live telemetry | Operations |
The CHANGE Scan Trigger
A decision rule for spending verification effort when a change materially affects product trust.
- Critical flow: Scan when authentication, authorization, billing, or data behavior changes.
- Handoff: Scan before accepting externally or AI-generated implementation work.
- Architecture: Scan after a meaningful cross-stack redesign.
- New release: Scan the candidate code before the release decision.
- Gap or surprise: Scan when observed behavior conflicts with expectations.
Trusted sources that inform this guide
These independent sources support the surrounding verification practices. AppTruth-specific product statements are product guidance and should be confirmed against current account or contractual documentation when formal assurance is required.
- Secure Software Development Framework (SSDF) — NIST. Defines outcome-based secure software development practices, including verification and release preparation.
- Testing for Reliability — Google SRE. Explains why multiple testing methods are needed to build confidence in production systems.
Related questions about “Is AppTruth continuous or on-demand?”
Does AppTruth automatically scan every commit?
No. The current workflow is user-initiated and on demand.
Should teams scan unchanged repositories repeatedly?
Usually no. A new scan is most useful after a material code change, a release milestone, a handoff, or a newly discovered uncertainty.