مواد ڏانهن وڃو

پليٽفارم جي بنيادي صلاحيت

ڏسو توهان جو سافٽ ويئر ڪيئن
پاڻ ۾ ڳنڍيل آهي.

Zof توهان جي خدمتن، API ۽ انحصارن جو نقشو ٺاهي ٿو ته جيئن توهان جي ٽيم ڄاڻي ته ڪا تبديلي اچڻ تي ڪهڙي شيءِ کي جاچڻو آهي.

  • تصديق جا ثبوت ۽ ڪنٽرول
  • انساني منظوري جتي پاليسي گهرجي
  • Works with GitHub

وقت سان لاڳاپيل

ڇا موجود آهي، ڇا بدليو، ڪڏهن ۽ ڪنهن بدلائي ڇڏيو

اثر جي حد

ڪارروائي هلڻ کان اڳ طئي ٿيل

پاليسيون

انهن نظامن سان ڳنڍيل جن جي اهي حفاظت ڪن ٿيون

مقرر دائري وارو

منظور ٿيل نظامن ۽ رسائي تائين محدود

What the graph holds

Entities, relationships, and time

توهان جي ريپوزيٽريز مان سروسز، اينڊ پوائنٽس، ڊيٽا اسٽور، انحصار ۽ مالڪ.

  • 01

    Relationships that carry consequence

    DEPENDS_ON, CALLS, READS, WRITES, DEPLOYS_TO, OWNED_BY, PROTECTED_BY, VERIFIED_BY, AFFECTS, GENERATED_BY, APPROVED_BY, USES_MODEL, USES_TOOL, SATISFIES, and VIOLATES.

  • 02

    Temporal by design

    What exists, what changed, when it changed, who or what changed it, what depended on it, what evidence existed, what policies applied, what decision was made, and what happened afterward.

  • 03

    Blast radius before action

    Every proposed change resolves to affected systems, criticality tier, applicable controls, historical incidents, and the verification required.

  • 04

    Shared by the whole loop

    Verification, evidence, and control all read from the same graph, so every decision is grounded in one understanding of the enterprise.

استعمال جون صورتون

اهي نتيجا جيڪي ٽيمون ماپن ٿيون

  • Size the blast radius before shipping

    See exactly which systems, data, and customers a change can affect, and how critical they are, before it is allowed to run.

    Tier 0

    criticality resolved
  • Require the right verification

    Controls mapped to affected systems determine the evidence a change must produce, so verification is targeted rather than exhaustive.

    Policy

    selects the evidence
  • Reconstruct any decision

    Walk back from an incident to the change, the evidence that existed, the policies that applied, and who approved it.

    Temporal

    history stays queryable
  • Give leadership one risk view

    One graph shows where risk concentrates, where controls apply, and what changed recently.

    One

    source of truth
Platform integration

The substrate of the control loop

The System Graph is not a standalone feature. Verification reads it to decide what must be proven, Evidence writes to it, and Control relies on it to size risk.

پليٽ فارم

Verification Engine

Selects the evidence each change requires from the systems and controls the graph resolves.

پليٽ فارم

Evidence

Every bundle, approval, and outcome is written back to the graph, so history is queryable.

پليٽ فارم

Control Plane

Policy decisions are grounded in criticality, affected systems, and incident history from the graph.

گورننس

هر اهم قدم تي انساني منظوري سان ضابطن هيٺ تصديق.

ڪنٽرول
  • توهان جي ڪنٽرول پرت هيٺ لڳاتار تصديق
  • System Graph تبديليون جاري ٿيڻ کان اڳ انحصارن جو نقشو ٺاهي ٿو
  • تعميل جي جائزي لاءِ آڊٽ جي معيار جا ثبوت
تصديق جا ثبوت · انساني منظوري · آڊٽ جا رڪارڊ

Detailed guide · English

In practice

Turn dependency context into a testing decision

The useful output of a graph is an explanation of why a change deserves attention. Start with a specific revision and follow the relationships that connect it to behavior your customers depend on. Treat missing relationships as an investigation task.

  1. 01

    Establish the starting point

    Identify the repository, base revision and proposed revision. Include configuration and dependency changes in the review scope, even when the application code diff is small.

  2. 02

    Follow the consequential paths

    Compare the reported affected areas with what the service owner expects. Ask which shared libraries, API consumers and background jobs could experience different behavior. Connected data sources determine which of these relationships are available.

  3. 03

    Choose checks and retain the rationale

    Use the dependency paths to select tests and reviewers. Record why each critical path was included. Keep a broader regression suite when unresolved dependencies make a narrower selection unreliable.

Illustrative scenario · not a customer result

A shared authentication library

A token parser changes in a library used by a web application and a background worker. A graph can help identify consumers represented in its inputs. Test valid, expired and malformed tokens in those consumers. If the worker relationship is absent, add it to the investigation rather than treating it as unaffected.

Questions to resolve before you begin

Is this a complete map of production?

Coverage depends on the connected sources and the relationships they describe. Static imports do not reveal every runtime call. Review source freshness and unresolved edges before relying on the map.

Does the graph replace observability?

Dependency context helps decide where to investigate and test. Production telemetry answers what is happening at runtime. Use both when assessing a release or investigating an incident.

اڳيون قدم

پنهنجو System Graph ڏسو

Reliability Sprint بڪ ڪريو ۽ Zof هڪ اهڙي نظام جو نقشو ٺاهڻ شروع ڪري ٿو جنهن جي ناڪامي توهان برداشت نٿا ڪري سگهو، اهم رستن ۽ خطري هيٺ آيل هنڌن جي سڃاڻپ ڪندي.

  • رسائي ۽ دائري جو جائزو وٺو
  • هڪ اهم نظام جو جائزو وٺو
  • خانگي تعيناتي جا اختيار
لائيو ڊيمو · نموني ڊيٽا

ڄاڻو ڇا بدليو. ڄاڻو ڇا ٽيسٽ ڪجي.

ٽاپولوجي-سمجھدار اثر تجزيو سروس تبديلين کي متاثر ٿيل ورڪ فلوز سان ڳنڍي ٿو ۽ سسٽم انحصار جي بنياد تي تصديق منصوبا تجويز ڪري ٿو.

تصديق کي ترجيح ڏيڻ لاءِ سسٽم سياق استعمال ڪريو.

01System Graph

هر تبديلي جو نتيجو سمجهو.

The System Graph maps services, endpoints, datastores, dependencies and owners from your repositories, so Zof knows what a proposed change could affect.

نتيجو

اثر جي حد

هر تبديلي لاءِ متاثر نظام، اهميت ۽ ڪنٽرول طئي ٿين ٿا.

وقت سان لاڳاپيل

ڇا بدليو، ڪڏهن، ڪنهن طرفان

تاريخ، ثبوت ۽ فيصلا ڳولا لائق رهن ٿا.

بنياد

هڪ گراف، مڪمل چڪر

تصديق، ثبوت ۽ ڪنٽرول ساڳيو ماڊل پڙهن ٿا.

MAPPED · LIVE/system-graph
Zof System Graph جو خاڪو، auth-service جي تبديلي جا اثر طئي ڪندي: Payment API، Checkout، Ledger ۽ Customer API متاثر طور نمايان، ڏيک ۾ Tier 0 جي اهميت، 7 متاثر نظام، 4 لاڳو ڪنٽرول، 2 تاريخي واقعا ۽ 6 گهربل تصديقون.
System Graph · تبديلي جو ممڪن اثر ڏيکاريندڙ خاڪو.