Skip to main content

Evidence Log

Purpose

This page tracks the evidence required before the Maqsafy technical documentation can move from an internal preliminary baseline to an approved internal technical baseline.

Evidence should be concise and sanitized. Do not include production secrets, customer data, private keys, access tokens, raw payment payloads, or unmasked screenshots.

Evidence Status

StatusMeaning
NeededEvidence has not been provided yet
ProvidedEvidence was provided and is linked or summarized
ReviewedEvidence was reviewed and accepted for documentation purposes
RejectedEvidence was not sufficient or was unsafe to include

Required Evidence Register

IDAreaEvidence NeededSuggested Evidence FormatOwnerStatusNotes
EVD-RBAC-001RBACPermission test evidence for Admin, School Manager, Supplier, and OperatorTest case names, screenshots with data masked, or CI outputCTO / BackendNeededInclude both positive and negative cases
EVD-TENANT-001Tenant isolationSchool user cannot access another school's dataNegative API test result or code referenceBackendNeededMust include expected 403 or equivalent denial
EVD-TENANT-002Tenant isolationSupplier cannot access another supplier's products, orders, invoicesNegative API test result or code referenceBackendNeededHigh priority
EVD-TENANT-003Tenant isolationOperator cannot access another operator's cafeteria recordsNegative API test result or code referenceBackendNeededHigh priority
EVD-CRED-001CredentialsCredential cancellation is Admin-onlyTest case or permission config evidenceBackend / ProductNeededSeparate cancellation from activation/deactivation
EVD-CRED-002CredentialsManager, Parent, and Student activation/deactivation behaviorPermission config or tested workflowsBackend / ProductNeededMust define exact allowed actions
EVD-BACKUP-001BackupLast database backup confirmationBackup job output or monitoring screenshotCTO / OperationsNeededMust not include credentials
EVD-RESTORE-001RestoreLast restore test date, environment, result, and validation checklistRestore test recordCTO / OperationsNeededRequired before final approval
EVD-RPO-001Recovery targetFormal RPO wordingApproved technical wordingCTONeededCurrent wording: zero data loss target
EVD-RTO-001Recovery targetRTO confirmationApproved technical wordingCTONeededCurrent target: less than 1 hour
EVD-PAY-001Payment idempotencyDuplicate callbacks/retries cannot duplicate wallet or ledger impactTest case, code reference, or reconciliation evidenceBackend / FinanceNeededHigh priority financial control
EVD-API-001API documentationOpenAPI / Swagger status/openapi.yaml draft and OpenAPI / Swagger documentation pageBackendPartialNeeds backend validation and hosted Swagger UI decision
EVD-SEC-001Security controlsCloudflare Access, auth, RBAC, rate limiting, and logging evidenceSanitized control checklistCTO / SecurityNeededNo secrets
EVD-MON-001MonitoringLaravel logs and Sentry operational evidenceScreenshot or alert configuration summaryCTO / OperationsNeededMask project DSNs
EVD-REL-001Release processDeployment, rollback, hotfix, and approval flowApproved process summaryCTO / ProductNeededRequired for operational readiness

Evidence Entry Template

Use this format when evidence is added.

## EVD-AREA-000 - Evidence Title

| Field | Details |
|---|---|
| Area | RBAC / Tenant Isolation / Backup / Restore / Payment / API / Security |
| Source | Test / Screenshot / Code reference / Team confirmation |
| Environment | Production / Staging / Local / Not applicable |
| Date | YYYY-MM-DD |
| Owner | Name or role |
| Result | Passed / Failed / Under Review |
| Sanitization | Sensitive data removed / Not applicable |
| Notes | Short summary only |

Evidence Rules

  • Do not attach real production secrets.
  • Do not include raw customer data.
  • Mask emails, phone numbers, names, tokens, payment references, and private URLs where possible.
  • Prefer test names, summaries, and screenshots over raw logs.
  • Evidence should support the documentation, not replace detailed internal operational records.