Perstein

ENGINEERING CHANGE WITH CONTEXT

Understand the impact before you change the code.

Scattered context makes change risky. Perstein connects code, architecture and work so you see evidence before people or agents act.

See how it works

git_push → symbol → CALLS → affected context

PERSTEIN / LIVE TRACEA real Orbit Source push becoming traceable context
A real Orbit Source push becoming traceable context: EVENT (git_push), SYMBOL (Server.handlePushEvent), CONSUMER (RunSingleProjectCodeGraphScan), CONTEXT (project + tenant + commit).
Inspect the intelligence flow
How it works

What Perstein is

The risky part of a change is what your tools cannot see.

Perstein connects code, architecture and engineering work so your team can review a change from real evidence before people or agents act.

  1. 01Map the structure

    Map the structure

    Orbit Graph identifies symbols, calls, routes, dependencies and impact from the repository itself.

  2. 02Connect the meaning

    Connect the meaning

    Zetalyra relates code to commits, work, decisions and organizational memory.

  3. 03Prepare the action

    Prepare the action

    Orbit Gravity selects grounded context and keeps human review available when evidence is not enough.

One traceable signal across three intelligence layers

How teams use Perstein

Make the next engineering decision with the people who own it.

The system gives your team a shared starting point: what changed, what it touches and what deserves review.

How teams use Perstein
  1. 01Before the change
  2. 02During the review
  3. 03After the decision
  1. 01

    Before the change

    The team sees the dependencies, rules and history that a ticket alone cannot show.

  2. 02

    During the review

    The people who own the system inspect impact together and decide what should happen next.

  3. 03

    After the decision

    The action, its context and the available evidence remain explainable to the team.

Architecture is a contract

Your architecture stays explicit as the system changes.

Define the rules your team uses. Perstein makes boundaries, ownership and violations visible before architectural drift becomes expensive.

Compliance profiles are configurable. Automated scaffolding and the default recommendation center on Vertical Slice Architecture (VSA).

Choose an architecture profile
Active contractVSAVertical slices + shared kernel
Allowed dependencyOwnership resolvedPolicy evaluated

Product evidence

Start with one change. Follow the evidence.

A push arrives, Perstein resolves the symbol, typed relations reveal impact, and the next action becomes reviewable.

Question
What happens after Orbit Source receives this push?
$perstein graph search --impact
Grounded result

The handler records the event, links commits to work and triggers an incremental Orbit Graph scan for the project.

Delivery statusEvidence linked, human review available
Evidence chain
  1. 01SymbolServer.handlePushEvent
  2. 02RelationCALLS
  3. 03ConsumerRunSingleProjectCodeGraphScan
  4. 04Eventgit_push
Next actionCreate a validation task in Orbit Workspace
ORBIT / READY
Built for controlled engineering change

Protection and traceability teams can understand.

Protected context
Sensitive context is handled with care

Sensitive telemetry is masked before analysis.

Authenticated boundaries
Service boundaries are protected

Requests to Perstein services are authenticated and rate-limited.

Traceable actions
Every action has a reason

Agent activity can be linked to the operation and evidence behind it.

Clear questions

Questions engineering teams ask before they start.

01What does Perstein replace or connect?

Perstein connects code, architecture and engineering work so teams can review change impact from one governed context. It complements the tools already used to build and operate software.

02Does Perstein force one architecture?

No. Teams configure compliance profiles for their chosen architecture. Automated scaffolding centers on Vertical Slice Architecture (VSA).

03How does Perstein understand an existing codebase?

Orbit Graph models symbols, calls, routes, dependencies and impact from the repository, then Zetalyra relates that structure to work, decisions and memory.

04Where does human review happen?

Orbit Gravity prepares grounded context and can keep a human in the loop when the available evidence is not enough for a confident next step.

05How do we evaluate it with our repository?

Start with one real change or architectural question. The Perstein team can use that starting point to show what context and evidence are available.

06What is available in Cloud, Code, CLI and MCP?

The same engineering context can be reached through Perstein Cloud, Code, CLI and MCP, with capabilities depending on the surface and workflow.

07What security and privacy controls are verified?

Verified surfaces include masked sensitive telemetry and authenticated, rate-limited service boundaries. We distinguish current controls from architectural principles and planned certifications.

Beta access for selected teams

Start with the change your team already needs to decide.

Request beta access to evaluate a real change with code, architecture and work in the same context — or talk to us about the transformation of your engineering organization.

Access is reviewed by the Perstein team. No account is created automatically.