Versioned test protocol

Operating evidence protocol v0.1

01

Direct comparison

Results enter a direct comparison only when fixture, protocol, tool meaning, main conditions, and cost cutoff are equivalent.

02

Default first

Test the configuration a new customer receives. Record every generally available onboarding or one-click change; separate expert tuning from the default batch.

03

Unknown stays unknown

A missing price, failed task, or unavailable test is published as a limit. It never becomes zero, pass, or implied superiority.

Eligible fixtures

Two workloads share the evidence structure.

WL-WP · v0.1Ten-site WordPress fixture→WL-PORTAL · v0.1Small client portal fixture→

Task definitions

Nine separate claims, nine separate records.

T01Cost & billing boundary+

Decision question

What must be paid to run the complete workload now, over 12 months, and at renewal?

Pass rule

Every required component has a price state, billing unit, quantity assumption, cash timing, and source date; unknown cost is not treated as zero.

Required record

  • First cash payment
  • 12- and 24-month cash cost
  • Renewal and usage assumptions
  • Required add-ons
  • Operator time kept separate
Limit

A price snapshot does not predict future vendor pricing or a visitor’s exact usage.

T02Bad update & code rollback+

Decision question

Can the operator return application code or site files to the last accepted release after a controlled bad update?

Pass rule

The reference workload returns to the accepted code version and its critical path completes without silently claiming that data or uploaded files were also restored.

Required record

  • Change introduced
  • Rollback operator and steps
  • Elapsed time
  • Failed steps
  • Application state after rollback
Limit

Code rollback is reported separately from database, file, and configuration recovery.

T03Database recovery+

Decision question

Can deleted or damaged synthetic records be recovered to a known restore point?

Pass rule

The expected records and relationships are present after recovery, with the restore point, elapsed time, help required, and data-loss window recorded.

Required record

  • Restore-point age
  • Self-service or assisted path
  • Elapsed time
  • Record reconciliation
  • Observed data loss
Limit

The task uses synthetic data and does not certify a visitor’s database design or legal retention process.

T04Uploaded-file recovery+

Decision question

Can a deleted or damaged synthetic upload be recovered independently of application code?

Pass rule

The expected file is readable after recovery and its metadata, restore source, elapsed time, and any overwrite risk are recorded.

Required record

  • File set and size
  • Restore mechanism
  • Elapsed time
  • Reconciliation result
  • Production overwrite risk
Limit

A successful small-file task does not establish performance or recovery behaviour for every storage volume.

T05Access boundary+

Decision question

Can one synthetic customer read another customer’s records or files through normal or direct paths?

Pass rule

Authorised paths work and attempted cross-customer record and file access is denied without exposing protected content.

Required record

  • Roles and tenants
  • Normal path
  • Direct record request
  • Copied file link
  • Administrator path
Limit

The result applies to the versioned fixture and configuration, not to arbitrary customer-written application rules.

T06Ownership & handover+

Decision question

Can a second authorised owner take control of accounts, billing, code, data, files, and credentials?

Pass rule

The new owner completes the documented administrator path and the original operator can be removed or their remaining dependency is explicitly recorded.

Required record

  • Transferable assets
  • Non-transferable dependencies
  • Billing control
  • Credential rotation
  • Acceptance checks
Limit

Actual ownership changes are performed only on authorised test accounts and do not prove contractual ownership for a visitor.

T07Routine operation+

Decision question

What recurring work remains for a small team without a dedicated infrastructure engineer?

Pass rule

A defined operator completes the representative update, alert review, user change, and support path while time and required expertise are recorded.

Required record

  • Task steps
  • Active operator time
  • Waiting time
  • Documentation used
  • Provider or developer escalation
Limit

A short observed task does not predict every incident or long-term staffing requirement.

T08Dependency boundary+

Decision question

Which builder, platform, account, integration, or paid service must remain for the workload to keep operating?

Pass rule

Every runtime dependency is classified as required, replaceable, exportable, or unknown, with an owner and exit consequence.

Required record

  • Runtime components
  • Account owner
  • Export path
  • Replacement path
  • Cancellation consequence
Limit

Documented portability is not treated as a completed migration until the replacement path is tested.

T09Critical path & loading+

Decision question

Do the important end-user paths complete under the fixed lab conditions, and what loading observations are repeatable?

Pass rule

Every critical step succeeds before loading observations are interpreted; five formal runs record median, minimum, maximum, and failures under the same stated conditions.

Required record

  • Fixture and release
  • Location and network condition
  • Critical-path outcome
  • Five formal observations
  • Mobile and reduced-network checks
Limit

This is a limited lab observation, not end-user field data, a long-term uptime percentage, or a high-concurrency load test.

Help improve this decision

Did this answer your question?