Skip to content
CCCrisisCore Systems
← Back to dossierBack to proof
Artifact viewer

Local authority vs cloud dependence diagram

Trust-boundary comparison between user authority and infrastructure dependence.

BLACKPAPER RESEARCHDIAGRAM 04Local Authority vs Cloud DependenceNot a moral binary. A structural contrast about what remains authoritative when conditions degrade.AUTHORITY STAYS CLOSEST TO THE USERModel A / Local AuthoritySERVICE REMAINS STRUCTURALLY UPSTREAMModel B / Cloud DependenceCONTROL SURFACEuser / deviceDEFAULT EXPOSUREminimalOFFLINE UTILITYhighRECOVERY PATHdirect + reversibleCOERCION RESISTANCEstrongerFAILURE BLAST RADIUScontainedCONTROL SURFACEservice / accountDEFAULT EXPOSUREpersistentOFFLINE UTILITYpartial or brokenRECOVERY PATHpolicy-mediatedCOERCION RESISTANCEweakerFAILURE BLAST RADIUSdistributedAUTHORITY AXISCRISISCORE-SYSTEMS / PROTECTIVE COMPUTINGcomparative systems plate
Raw fileGitHub mirror ↗
What this artifact proves

This artifact shows how CrisisCore turns an abstract trust claim into a reviewable product boundary.

Use this when your product has to explain:

  • • what data crosses a boundary
  • • what stays local
  • • what fails under pressure
  • • what evidence a buyer can inspect
  • • what should be fixed before launch

Need this mapped for your product?

Send the URL, launch stage, and one concern. I'll return the first 3 trust risks and the smallest useful next step.

Get a 3-point risk read

Need this packaged for buyer review?

See the CrisisCore Defensibility Packet.

Open Defensibility Packet
Continue inspection

Move from the single artifact back to the surrounding proof surface, dossier, and writing trail.

Open dossierOpen proofOpen sitemap
Related artifacts
Protective computing lifecycle diagram