A design gate that defines who may upload, view, redact, retain, approve, export, or delete QA evidence before FAEDA builds real evidence storage.
Evidence candidates
21
from Phase 174 QA desk
Permission actions
8
upload, view, redact, approve, retain
Storage lanes
5
visual, notes, boundary, mobile, decision
Runtime storage
0
design only
Storage lanes
Screenshots or capture references showing layout, mobile fit, overlapping text, clipped actions, or route rendering.
No CNIC, wallet PIN, bank info, private customer data, provider secrets, or real credentials.
Human QA notes explaining pass/fail/correction status and what a developer must inspect next.
No personal attacks, unverified legal claims, private financial data, or raw backend errors.
Evidence that a route does not overclaim auth, payment, settlement, ledger, inventory, order, PO, GRN, invoice, or founder authority.
No production payment screenshots, bank statements, live keys, or customer-private ledger exports.
Mobile-width evidence for tap quality, readable text, visible actions, and no horizontal overflow.
No device personal notification content, browser passwords, or private app state.
Final manual decision: pass, needs correction, accepted preview-only, blocked, or recheck after fix.
No silent approval, no retroactive pass without evidence, no unassigned reviewer decision.
Permission actions
Allowed for
Requires
Blocked for
Allowed for
Requires
Blocked for
Allowed for
Requires
Blocked for
Allowed for
Requires
Blocked for
Allowed for
Requires
Blocked for
Allowed for
Requires
Blocked for
Allowed for
Requires
Blocked for
Allowed for
Requires
Blocked for
Role permission matrix
Business roles should not receive raw QA evidence authority until backend RBAC and privacy scope exist.
Upload
no
View
own role-safe public evidence later
Approve
no
Redact
no
Export
no
Business roles should not receive raw QA evidence authority until backend RBAC and privacy scope exist.
Upload
no
View
own role-safe public evidence later
Approve
no
Redact
no
Export
no
Business roles should not receive raw QA evidence authority until backend RBAC and privacy scope exist.
Upload
no
View
own role-safe public evidence later
Approve
no
Redact
no
Export
no
Business roles should not receive raw QA evidence authority until backend RBAC and privacy scope exist.
Upload
no
View
own role-safe public evidence later
Approve
no
Redact
no
Export
no
Business roles should not receive raw QA evidence authority until backend RBAC and privacy scope exist.
Upload
no
View
own customer-safe support evidence later
Approve
no
Redact
no
Export
no
Business roles should not receive raw QA evidence authority until backend RBAC and privacy scope exist.
Upload
no
View
own role-safe public evidence later
Approve
no
Redact
no
Export
no
Founder/Admin can govern evidence but still needs maker-checker and audit trails.
Upload
yes
View
all assigned evidence
Approve
maker-checker only
Redact
with security reviewer
Export
redacted only
Privacy classes
Can be used in demos after review.
Visible only to assigned QA, founder/admin, and approved developers.
Requires security/data reviewer approval and redaction before sharing.
Must not be uploaded. If discovered, redact/incident flow must be triggered.
Governance workflow
Mark evidence as public-safe, internal, restricted, or forbidden before upload is ever allowed.
No unclassified evidence enters storage.
Confirm the user has route scope, role scope, and evidence action permission.
Upload/view/redact/approve/export/delete actions are not UI-only.
Restricted evidence must be redacted or locked before broader review.
Sensitive data is protected before sharing.
Approvals, exports, deletion, restoration, and restricted evidence decisions require checker review.
No silent evidence approval or deletion.
Set retention duration, deletion review date, and audit trail before evidence is considered governed.
Evidence storage stays privacy-aware and reviewable.
Hard rules
Phase 175 is a permission design gate only.
Do not build storage buckets, upload APIs, download APIs, database tables, file writers, queues, workers, or evidence mutations here.
No real screenshots, CNIC, wallet, bank, customer private data, supplier secrets, provider keys, or production credentials may be stored in this phase.
UI visibility must never replace backend RBAC, storage ACLs, audit logs, retention rules, and maker-checker approval.
Next gate can design the evidence data contract only after these permissions are accepted.
Permission packet
{
"permissionGateId": "evidence_storage_permission_design_gate_175",
"phase": "Phase 175",
"sourceGate": "FAEDA-ROLE-QA-EVIDENCE-CAPTURE-001",
"route": "/business-pro/evidence-storage-permission-design-gate",
"evidenceDesk": "role_qa_evidence_capture_desk_174",
"designOnly": true,
"createsStorage": false,
"createsUploadApi": false,
"createsDatabase": false,
"createsFiles": false,
"permissionActions": [
"Upload evidence",
"View evidence",
"Redact evidence",
"Approve evidence",
"Retain evidence",
"Export evidence",
"Delete evidence",
"Restore evidence"
],
"storageLanes": [
"visual-screenshot",
"review-note",
"boundary-proof",
"mobile-proof",
"review-decision"
],
"privacyClasses": [
"Public-safe",
"Internal",
"Restricted",
"Forbidden"
],
"evidenceCandidateCount": 21,
"nextAllowedGate": "phase_176_evidence_data_contract_design"
}Next build gate
After permission rules are clear, the next safe move is a schema/API contract design for evidence metadata without implementation.