Want to understand the product better?

Is Fractalis a B2B product?

Yes. Fractalis is built for software organizations: CTOs, VP Engineering leaders, directors, engineering managers, tech leads, and the engineers whose work creates the signals.

It is not a consumer product.

Is Fractalis an engineering analytics platform?

Fractalis uses engineering data, but it is not primarily an engineering analytics dashboard.

Analytics usually answers, “What happened?”

Fractalis is designed to answer, “What does this mean, what changed, what evidence supports it, and who can still act?”

This is why Fractalis is better understood as engineering intelligence or an operating intelligence layer, not a traditional analytics product.

What do you mean by engineering intelligence?

Engineering intelligence means turning distributed engineering work signals into evidence-backed understanding and action.

It is not just counting activity. It connects events, timing, relationships, context changes, contribution signals, capability movement, and risk patterns across the tools where work already happens.

The goal is to help software organizations understand the engineering system earlier and more coherently than dashboards, status meetings, or manual context reconstruction can.

What do you mean by an operating intelligence layer?

Fractalis sits above the tools where engineering work happens and builds a coherent representation of the work system from events, relationships, timestamps, links, conditions, and evidence.

It does not replace GitHub, Jira, Figma, Slack, Notion, or Confluence. It reads the signals those systems already produce and explains what they mean together.

The relevant information often already exists. The problem is that it is distributed.

Is Fractalis an AI platform?

No. Fractalis is an engineering intelligence platform.

Its core intelligence comes from proprietary, patent-pending deterministic systems that normalize events, evaluate patterns, attach evidence, and route insights to the right organizational altitude.

AI may be used where it improves explanation, synthesis, or user experience, but AI is not the category, not the core claim, and not the source of truth.

Is Fractalis an AI coding tool?

No. Fractalis does not write code, generate pull requests, replace developers, or act as an AI pair programmer.

It is not a Copilot, Cursor, Devin, or coding-agent alternative.

Fractalis sits above tools like GitHub, Jira, Figma, Notion, Slack, and Confluence and reads what is already happening across them.

Does Fractalis do AI-assisted software engineering?

No, not in the way that phrase is normally used.

Fractalis does not generate requirements, code, architecture, or documentation for teams. It helps organizations understand whether the work already happening is aligned, sustainable, high-quality, and developing the right capabilities.

Where does AI fit, if at all?

AI may be used as an assisting layer where it helps translate, summarize, or improve the user experience.

But the Fractalis intelligence layer is structured, auditable, evidence-backed, and governed by deterministic systems. The source of truth is the evaluated evidence, not generated prose.

What is Fractalis?

Fractalis is a trust-first engineering intelligence platform for software organizations.

It connects the tools teams already use and turns fragmented work signals into evidence-backed insights, predictive guidance, and transparent growth intelligence.

What does Fractalis do in simple terms?

Fractalis tells software teams when reality changed, what is likely to happen next, and where to act before the cost lands.

A design changed after implementation started. A ticket was cancelled while code is still being written. Review load is concentrating around one expert. An engineer's growth evidence is invisible before a career conversation.

Fractalis connects those signals across tools and turns them into evidence-backed action.

What are the main kinds of intelligence Fractalis provides?

Fractalis produces three connected forms of intelligence from the same evidence base.

Operational intelligence: drift, bottlenecks, review pressure, knowledge concentration, stale context, blocked dependencies, fragile ownership, quality pressure, and delivery risk.

Growth intelligence: contribution visibility, skill and competency evidence, role-fit movement, current-role gaps, target-role guidance, and evidence for better career conversations.

Leadership intelligence: aggregate system patterns, structural risks, team capability movement, investment signals, cross-team friction, and organizational health trends.

These are not three separate products stitched together. They are different readings of the same engineering reality.

What problem does Fractalis solve?

Engineering teams are not short on data. They are short on early, coherent truth.

Important signals about drift, bottlenecks, coordination, knowledge concentration, and growth are scattered across GitHub, Jira, Figma, Notion, Slack, Confluence, and people's heads.

By the time a dashboard metric moves, the waste is usually already paid for.

What does “the truth changed” mean?

It means the reality around active work changed after the team started acting on an earlier version of that reality. For example:

• a Figma design changed after implementation began
• a ticket was cancelled while code is still being written
• a spec was updated after engineering started
• a reviewer became overloaded while the PR queue kept growing
• documentation linked to active work became stale
• a decision changed but execution continued on the old assumption

Does Fractalis replace Jira, GitHub, Slack, Figma, Notion, or Confluence?

No. Fractalis does not ask teams to replace their workflow stack.

It sits across the stack, reads the events those tools already produce, connects the dots between them, and surfaces the patterns no single tool can see alone.

Is Fractalis only for managers and executives?

No. Fractalis is designed for the whole engineering organization: engineers, tech leads, managers, directors, VP Engineering, and executives.

Each role needs different intelligence from the same work reality.

An engineer needs to know what changed in the work they are doing, where they are blocked, what needs attention, and how their work contributes to growth. A manager needs to know where to intervene, who needs support, what risks are forming, and how to prepare better conversations. A director needs to see patterns across teams. Executives need to understand what is compounding at the system level.

What does role-tailored intelligence mean?

It means the same underlying reality is interpreted for the person who sees it. A stale design may mean:

• for an engineer: check the updated design before continuing
• for a manager: this workstream may need a design-engineering sync
• for a director: this team has a recurring design handoff problem
• for an executive: this area has a cross-functional alignment risk affecting delivery confidence

Same evidence. Different altitude. Different action.

How does Fractalis improve productivity?

Not by pushing people to do more activity.

Fractalis improves productivity by reducing the hidden work of finding, connecting, and interpreting context. Teams already lose time switching between tools, reconstructing what changed, discovering stale assumptions too late, and turning scattered signals into decisions.

Fractalis does that connective work continuously and turns it into actionable intelligence.

Does Fractalis just aggregate data from many tools?

No. Aggregation is not enough.

Putting GitHub, Jira, Figma, Notion, Slack, and Confluence into one place still leaves the user with the hardest job: connecting the dots.

Fractalis is designed to do that reasoning work: linking events, comparing timing, identifying patterns, attaching evidence, and routing the right intelligence to the right role.

Is Fractalis watching me?

No. Fractalis is not a surveillance tool.

It does not track keystrokes, working hours, active minutes, message volume, screen activity, meeting attention, or how fast you respond.

Fractalis reads work artifacts and events so it can help you understand what is happening around your work, what changed, what might affect you, and what evidence your work is creating.

Can my manager see more about me than I can see about myself?

No. This is one of the core trust rules.

If Fractalis shows something about you to your manager, you should be able to see the same thing yourself: the same signal, the same evidence, the same context.

There are no hidden manager-only scores about you.

How does Fractalis help an engineer day to day?

It helps you see context that is usually scattered or easy to miss. For example:

• the design changed after engineering work started
• the spec was updated after you began implementation
• the ticket moved or changed while code is still being written
• your PR is waiting on a reviewer who is overloaded
• related discussion happened in Slack, Notion, or Confluence
• documentation connected to your work may be stale
• a dependency is blocked elsewhere

The goal is to reduce surprise rework and help you act earlier.

How does Fractalis make my work visible?

A lot of valuable engineering work is quiet.

Reviewing thoughtfully. Catching architectural issues. Mentoring someone in a PR. Cleaning up a fragile part of the system. Owning a messy handoff. Reducing risk before it becomes visible. These things often disappear by the time annual reviews or career conversations happen.

Fractalis keeps evidence connected to the work as it happens, so your contribution does not depend on memory, self-promotion, or someone digging through old tickets and messages months later.

What if I am a quiet contributor?

Fractalis is especially valuable for quiet contributors.

Some of the highest-value engineering work is not loud. It does not always show up as the biggest feature, the most commits, or the flashiest demo.

Fractalis helps surface evidence of invisible work: review depth, system support, coordination, risk reduction, mentoring, ownership, and steady growth.

The point is not to rank you. The point is to make sure your real contribution is not lost.

Do I have to collect evidence manually?

No. That is exactly what Fractalis is trying to avoid.

Today, engineers often have to reconstruct their impact by searching old PRs, Jira tickets, Slack threads, docs, emails, and calendar notes. Fractalis connects that evidence as the work happens, so career conversations can be grounded in reality instead of memory.

How does Fractalis help with my growth?

Fractalis helps turn your real work into a clearer growth path.

It can show which skills and competencies your work is already demonstrating, where you are building momentum, where gaps still exist for your current role, and what may matter for the next role on your career path.

Instead of guessing what to improve or waiting for a yearly review, you get a clearer picture of what is actually moving.

Fractalis does not turn growth into a hidden score. It surfaces evidence, direction, gaps, and recommendations so you can make better decisions about your own development.

What kind of growth evidence does Fractalis use?

Fractalis looks for evidence already present in real work: the work someone ships, reviews, supports, documents, improves, coordinates, or helps others understand.

That evidence can point to technical skills, domain knowledge, collaboration, ownership, review quality, mentoring, architectural judgment, and other capability areas.

The point is not to decide whether a person is “good” or “bad.”

The point is to make growth more visible, explainable, and useful in the moments where it matters.

How does Fractalis keep growth explainable?

Growth intelligence should never ask the user to trust an unexplained number.

When Fractalis surfaces a growth signal or recommendation, it should show:

• what capability area it relates to
• what work evidence supports it
• why it matters for the user's goals
• how confident the signal is
• what practical next step could help

The goal is not to produce a mysterious score. The goal is to make career conversations more specific, more timely, and better grounded in real work.

Does Fractalis tell me what to work on next?

Yes, but as guidance, not pressure.

Fractalis can recommend focus areas based on your goals, your current evidence, your role expectations, and the gaps that would matter most.

The goal is to help you spend effort where it actually changes your trajectory, not overwhelm you with generic advice.

How does Fractalis recommend growth actions?

Fractalis compares current evidence against the user's selected goals or role direction.

It can identify missing or weak evidence areas, then suggest actions likely to create useful evidence for that path.

For example, it may point toward deeper review practice, more ownership in a certain area, stronger documentation, broader domain exposure, mentoring opportunities, or focused learning.

The recommendation should show why it matters: which gap it connects to, which direction it supports, and what kind of evidence the action would help create.

This is guidance, not assignment. The user stays in control.

Can Fractalis help me prepare for my next role?

Yes. Fractalis can connect your current work evidence to the capabilities expected in your current role and potential next roles.

That means you can see what is already strong, what is missing, and which next steps would create the most useful evidence. For example: deeper review practice, architecture ownership, mentoring, domain exposure, testing discipline, documentation, or a specific skill area.

Does Fractalis decide whether I am ready for promotion?

No. Fractalis does not issue promotion verdicts.

It can surface evidence, capability signals, and gap movement that may support a career conversation.

But promotion, leveling, performance, and career decisions remain human decisions. They require context, judgment, calibration, and conversation.

Fractalis is designed to make those conversations better grounded, not automatic.

What does role-fit or readiness indicator mean?

A role-fit or readiness indicator is not a verdict.

It means Fractalis has found evidence that may be relevant to a role expectation or capability area.

For example, a role may require deeper review practice, architectural ownership, mentoring, domain judgment, incident response, testing discipline, documentation, or cross-team coordination.

Fractalis can connect work evidence to those capability areas and show where evidence is strong, weak, missing, or improving.

It should not say, “you are ready for Staff Engineer.” It should say, “these evidence areas are moving toward Staff-level expectations, these areas still need stronger evidence, and here are practical next steps.”

How does Fractalis avoid confusing loud activity with real growth?

Fractalis should not treat volume as growth.

More commits, more comments, or more tickets do not automatically mean stronger capability.

Growth intelligence should look for evidence quality and patterns over time: substantive review, ownership, risk reduction, knowledge sharing, mentoring traces, architectural reasoning, gap closure, repeated capability use, and role-relevant progression.

That evidence should include confidence and context so the user can understand why a recommendation appeared.

Can Fractalis help me change career direction?

Yes. Fractalis can help you explore and move toward a new target role.

If you want to shift from backend engineer toward staff engineer, engineering manager, platform engineer, product-minded technical lead, security specialist, or another role path, Fractalis can compare your current evidence against the capabilities that role requires.

It can show what already transfers, what gaps matter most, and what kind of work or learning would help you build the missing evidence.

Can I set a target role?

Yes. You should be able to set or explore target roles that matter to you.

Once a target role is selected, Fractalis can help you understand your current fit, the gap between where you are and where you want to go, and which actions would move you closer.

This turns career movement from vague ambition into an evidence-backed path.

What if I am not ready to share my target role with my manager?

That should remain under your control.

Exploring a new role can be sensitive. Fractalis should support private exploration first. You can use it to understand possible paths, compare options, and decide when or whether to share a direction with your manager.

Does this force me into a career path?

No. The growth layer should be user-centered.

Fractalis helps you understand possible paths and the evidence behind them. You can move at your own pace, focus on the goals that matter to you, and use recommendations as a guide rather than a mandate.

How does Fractalis help engineering managers?

Fractalis helps managers stop reconstructing context manually.

A manager usually has to jump between GitHub, Jira, Slack, docs, calendar notes, old 1:1s, and memory just to understand what changed for each person.

Fractalis does that connective work continuously. It surfaces what needs attention, why it matters, what evidence supports it, and what follow-up may be needed.

How does Fractalis help with 1:1s?

Fractalis helps prepare better 1:1s from real work context.

It can surface recent work, growth signals, blockers, recognition moments, workload patterns, stalled goals, follow-ups from past conversations, and suggested discussion points.

Instead of walking into a 1:1 trying to remember what happened, the manager starts with evidence and context.

Does Fractalis replace the manager's judgment?

No. It supports the manager's judgment.

Fractalis does not tell a manager what to think about a person. It provides evidence, patterns, and suggested actions so the manager can have a better human conversation.

The manager still brings context, empathy, and judgment.

Fractalis is a lens, not a judge. It helps managers see patterns they may otherwise miss, but it does not replace their responsibility to interpret those patterns carefully.

How does Fractalis help managers remember follow-ups?

It keeps important threads from disappearing.

If a manager discussed a growth area, a blocker, a recognition moment, an onboarding issue, or a career goal, Fractalis can help keep that context connected to future conversations.

The goal is to prevent “we talked about this three months ago and forgot” from becoming the default management pattern.

How does Fractalis help with recognition?

Fractalis helps managers see contribution that is easy to miss.

Not every important contribution is loud. Some people reduce risk, unblock others, review deeply, mentor quietly, stabilize messy systems, or hold a team together through coordination work.

Fractalis helps surface that evidence so managers can recognize people more fairly and more often.

Can Fractalis help identify hidden contributors?

Yes. This is one of the most important manager benefits.

Fractalis can help reveal the people whose work does not always show up in obvious output metrics: thoughtful reviewers, system maintainers, mentors, dependency untanglers, people who prevent rework, and contributors who strengthen the team without always owning the flashiest feature.

How does Fractalis help managers understand team gaps?

Fractalis can show where team capabilities are strong, where gaps are forming, and where knowledge is too concentrated.

That helps managers set team-wide focus areas, plan mentoring, rebalance opportunities, support hiring discussions, and make development more intentional.

Instead of guessing “we probably need more backend depth,” a manager can see which capabilities are actually missing or fragile.

Can Fractalis help set team focus areas?

Yes. Fractalis can help translate team patterns into practical focus areas.

If review quality is weakening, knowledge is concentrated, design handoffs are causing drift, or a capability gap is slowing delivery, Fractalis can help managers identify the theme and define a team-wide focus area that addresses the real issue.

How does Fractalis help directors?

Directors need to understand what is repeating across teams.

Fractalis helps directors see aggregate patterns across squads, tribes, or areas: recurring delivery friction, capability gaps, knowledge concentration, uneven recognition, cross-team coordination issues, repeated process breakdowns, and risks that are larger than one manager's team.

A director does not need to inspect every individual event. They need to know where the system is bending, which teams need support, and whether a problem is isolated or becoming structural.

What does a director see if they do not see individuals?

They see team-level and cross-team intelligence. For example:

• which teams are accumulating delivery risk
• where review bottlenecks keep recurring
• where capability coverage is thin
• where knowledge silos are forming
• where recognition or opportunity looks uneven
• where handoffs between teams keep breaking
• where managers may need support or calibration
• where a pattern has repeated enough to become a leadership problem

The view is aggregate, but not vague. The evidence is still there, just rolled up to the level where a director can act.

How does Fractalis help VP Engineering leaders?

A VP Engineering leader needs portfolio visibility: what is moving, what is fragile, what is compounding, and where leadership intervention changes the outcome.

Fractalis can show portfolio health across teams: delivery confidence, capacity pressure, capability direction, ownership continuity risk, cross-team dependency risk, quality movement, and organizational patterns that are not visible from a single team dashboard.

The VP does not need “what did this engineer do yesterday?” The VP needs “which parts of the engineering system are strengthening, which are becoming fragile, and where should we invest attention?”

How does Fractalis help C-level leaders?

C-level leaders need system-level intelligence.

Fractalis helps them understand whether the engineering organization is becoming more capable, more aligned, more resilient, or more fragile.

It can surface aggregate trends around delivery health, risk convergence, capability coverage, investment balance, quality, and organizational pressure.

This is especially useful for strategic questions: where are we underinvested, where are we overloading the system, what risks are likely to compound, and what capability gaps may affect future execution?

Does aggregate mean vague?

No. Aggregate means the intelligence is shown at the right altitude.

A manager may need a named signal about a direct report. A director needs to know that three teams are showing the same handoff failure. A VP needs to know that a portfolio has declining release confidence. A CTO needs to know that a capability gap is becoming a strategic risk.

Same evidence. Different altitude. Different action.

Can leaders still understand the evidence?

Yes. Fractalis should preserve the evidence chain even when the view is aggregated.

A director or VP should be able to understand why a signal exists: which teams, which time window, which categories, which patterns, which trend, which related insights.

They do not need private individual surveillance to understand the system.

What kinds of decisions does Fractalis support at leadership level?

Leadership-level decisions include:

• where to invest capacity
• where teams need support
• where capability gaps affect delivery
• where knowledge silos create continuity risk
• where process breakdowns are repeating
• where recognition or opportunity is uneven
• where hiring or internal mobility should be prioritized
• where delivery confidence is weakening
• where intervention is needed before risk compounds

How does this differ from normal executive dashboards?

Normal dashboards show metrics. Fractalis shows connected intelligence.

A dashboard may show that cycle time changed. Fractalis can connect that to review pressure, scope drift, decision delays, capability gaps, and recurring team patterns.

Leadership does not just see what moved. They see why it may be moving and what kind of action belongs at their altitude.

Do you provide engineering metrics?

Yes. Fractalis provides the engineering metrics buyers expect: delivery flow, cycle time, review pressure, WIP, deployment patterns, quality signals, traceability, and related operational measures.

But metrics are not the core of Fractalis. They are the baseline layer.

The real value is what sits above them: evidence-backed insights, cross-tool drift detection, growth intelligence, altitude-aware routing, and action paths.

Are metrics the main product?

No. Metrics are necessary, but they are not enough.

A metric can tell you that cycle time increased. Fractalis is built to tell you why it may have increased, what evidence supports that explanation, what changed across the workflow, who is positioned to act, and what is likely to happen if nobody intervenes.

How are Fractalis metrics different from normal dashboards?

Most dashboards show numbers. Fractalis connects numbers to evidence.

A Fractalis metric should not be a floating score. It should connect back to the events, artifacts, time windows, and patterns that produced it.

Users should be able to understand the “why behind the number,” not just stare at a chart and guess.

What does “evidence-backed” mean?

It means an insight or metric is tied to the work signals that caused it.

For example: a review bottleneck is not just “review is slow.” It can be backed by aging PRs, reviewer load, affected work items, review history, changed scope, and related signals.

The user can see the trail instead of being asked to trust a black box.

How is Fractalis different from engineering analytics dashboards?

Traditional engineering analytics tools are mostly retrospective. They tell leaders what happened: cycle time went up, work in progress increased, review time got slower, delivery changed.

Fractalis is designed to answer the next question: what does this mean, what caused it, what is likely next, and where can we act before the cost compounds?

How is Fractalis different from developer productivity tools?

Fractalis is not built to rank developers or measure raw output. It is not trying to squeeze more activity out of engineers.

Fractalis reads the engineering system: alignment, drift, quality, capacity, growth, risk, and trust.

It helps teams understand whether work is healthy, whether people are growing, and whether reality has changed underneath active work.

Can existing dashboard tools just add more metrics?

They can add metrics. Metrics are comparatively easy to copy.

What is harder to copy is the combination Fractalis is built around: cross-tool temporal correlation, evidence chains, deterministic insight evaluation, skills-and-growth intelligence, role-aware routing, and a trust model that refuses surveillance patterns.

Why is cross-tool intelligence different from a data warehouse?

A data warehouse can collect events from many tools. That does not automatically produce useful intelligence.

Fractalis is not just collecting data. It is evaluating how events relate across time and context.

If code starts Tuesday and the linked design changes Thursday, the important thing is not that both events exist. The important thing is that their order creates risk.

How does Fractalis avoid alert fatigue?

By treating insights as decision moments, not notification volume.

The goal is not to show every possible warning. The goal is to surface the few signals that matter now, with severity, confidence, evidence, and a clear action path for the person who can actually do something about them.

Do you compare engineers against each other?

No. Fractalis refuses stack ranking and individual productivity leaderboards.

The product can show an engineer their own evidence and can help a manager support their direct reports, but it is not a “bottom 20%” machine.

That would break the trust model and distort behavior.

Why should users trust a Fractalis insight?

Because an insight is not a vague AI opinion.

A Fractalis insight is produced from defined conditions, evaluated against real work events, and attached to evidence.

Every insight should answer:

• what pattern was detected
• which conditions caused it to fire
• which events or artifacts support it
• how severe it is
• how confident the system is
• what action path makes sense next

The user should never have to wonder, “Where did this come from?”

What does confidence mean?

Confidence describes how strong the evidence behind an insight is.

It can reflect whether the evidence is fresh, complete enough, corroborated across tools, connected by clear timing relationships, and aligned with the conditions that caused the insight to fire.

Confidence is not a decorative label. It helps users understand how much weight to give an insight and whether they should act, investigate, or wait for more evidence.

How does Fractalis avoid false positives?

Fractalis reduces false positives by grounding insights in explicit conditions and evidence chains.

An insight should not fire just because something “sounds risky.” It should require enough supporting events, relevant timing, severity thresholds, and context to justify surfacing it.

The evidence is visible so users can inspect, challenge, confirm, or dismiss the insight. That feedback is important because engineering intelligence must remain useful, not noisy.

Are Fractalis insights black-box AI outputs?

No. Fractalis insights are not freeform AI judgments.

The core insight system is deterministic: when the same conditions are met against the same evidence, the same insight fires.

That consistency matters because teams need to trust the system as an operational instrument, not treat it as a mysterious opinion generator.

What does deterministic mean in practice?

It means Fractalis does not randomly decide that something “looks risky.”

An insight fires because explicit conditions were met.

For example, a work item may be active, linked context may have changed after implementation began, and the evidence window may show enough supporting events to cross a severity threshold.

If those same conditions happen again, the same kind of intelligence fires again.

Does Fractalis show the evidence behind an insight?

Yes. Evidence is part of the product, not an optional debug mode.

A user should be able to inspect the chain of events that led to an insight: the ticket update, the design change, the pull request, the review pattern, the stale documentation, or the growth signal that contributed to the detection.

The insight is the headline. The evidence chain is the reason to trust it.

How is this different from an AI summary?

An AI summary can be useful, but it often asks the user to trust generated language.

Fractalis starts from structured intelligence. The system detects patterns from defined conditions and evidence.

Any narrative layer should explain or translate that intelligence, not invent it.

Why does repeatability matter?

Because engineering teams cannot run on vibes.

If the same evidence produces different conclusions depending on wording, timing, or a model's mood, people stop trusting the system.

Fractalis is designed so the intelligence layer behaves consistently.

Same conditions, same insight. Different evidence, different result. That is what makes it auditable and operationally useful.

Is Fractalis employee surveillance?

No. Fractalis is built around the opposite posture: the employee sees what the manager sees about them, and the product surfaces evidence rather than secret judgments.

It is designed to create shared context, not hidden monitoring.

What does Fractalis refuse to compute?

Fractalis refuses surveillance-shaped capabilities, including:

• working-hours tracking
• keystroke, attention, or active-minutes monitoring
• message-volume scoring per person
• sentiment analysis on individuals
• per-person AI token or Copilot leaderboards
• stack ranking
• auto-generated PIP packets or performance review text

Can an employee see what their manager sees?

Yes. That is one of the core trust rules.

If Fractalis computes something about an IC for their manager, the IC should be able to see the same evidence, at the same level of detail, in their own view.

Does Fractalis label people as underperforming, disengaged, or burned out?

No. Fractalis avoids interpretive labels.

It can surface observed patterns with evidence, severity, and confidence: sustained overload, stalled growth signals, review concentration, or recognition gaps.

The manager still has to interpret the situation with human context.

Does Fractalis evaluate people?

No. Fractalis is not designed to rank, score, or judge people.

It can surface evidence-backed signals about work, contribution, growth, overload, risk, and capability movement. But it does not decide whether someone is good, bad, promotable, underperforming, or disengaged.

Fractalis is a lens, not a judge. It helps people see the system more clearly so human conversations and decisions can be better informed.

Who can see named individual data?

Names appear when the viewer is the correct intervention owner.

An IC sees their own data. A manager sees named direct reports. Directors and executives see aggregate patterns by default.

Named exceptions at higher altitude should be tightly limited and logged.

Does Fractalis create performance reviews?

No. Fractalis can provide evidence a manager may choose to use in a human conversation, but it does not write performance reviews, produce termination- risk labels, or generate PIP ammunition.

The product is built for intervention and development, not automated judgment.

What is an insight?

An insight is a deterministic, evidence-backed detection.

It is not a vibe, a hidden opinion, or a black-box label.

An insight explains what pattern fired, which evidence triggered it, how severe it is, how confident the system is, and what action is likely to help.

What is a signal?

A signal is evidence about a person, skill, work item, or system state.

For career intelligence, signals feed skill mastery and role-fit movement.

For operational intelligence, signals feed detections like drift, stalled work, review bottlenecks, and process breakdown.

What is the difference between a metric and an insight?

A metric is a number: cycle time, deployment frequency, WIP, traceability percentage.

An insight is a decision prompt: what changed, why it matters, what evidence backs it, and what to do next.

Metrics establish context. Insights drive action.

What are the Fractalis 8 Lenses?

The 8 Lenses are the decision questions Fractalis organizes intelligence around:

• Flow: Is delivery moving?
• Quality: Is what we ship holding up?
• Drift: Is what we built what we said?
• Discipline: Is the plumbing real?
• Capacity: Is bandwidth and knowledge sustainable?
• Growth: Is the team getting stronger?
• Equity: Is recognition and opportunity fair?
• Risk: What is about to break?

Is the Risk lens about people?

Not primarily. In the 8 Lenses methodology, Risk is entity-level and system-level.

Risk looks at convergence, mitigation accountability, and pattern repetition:

• are multiple moderate or severe insights firing against the same workstream, team, component, release, capability area, or operational entity?
• has a mitigation been committed but left unresolved for too long?
• has the same pattern fired, been resolved, and then returned within the analysis window?

People-related evidence may contribute indirectly through other lenses, such as Capacity, Growth, or Equity. For example, knowledge concentration belongs primarily to Capacity, and role-fit movement belongs to Growth.

But the Risk lens itself should not be framed as “which person is risky.” It asks where the system is converging toward breakage and whether action is still possible.

Are the 8 Lenses eight different products?

No. This is important.

The 8 Lenses are not eight separate products stitched together. They are eight ways to interrogate the same operational reality.

The same underlying evidence graph can reveal flow problems, quality pressure, drift, capacity risk, growth movement, recognition gaps, and leadership risk depending on which question is being asked.

That is why the lenses are powerful: they organize one coherent representation of the engineering system into the decision questions different roles actually need.

What is altitude?

Altitude is the viewer's organizational height.

ICs see their own work and squad context. Managers see named directs. Directors see aggregate team patterns. Executives see system-level signals.

The same underlying insight can render differently at each altitude because the action owner is different.

What does predictive or what-if guidance mean?

Predictive guidance asks what is likely to compound if nobody acts.

What-if guidance helps compare a possible intervention before the team invests effort.

For example: what changes if a specific skill gap closes, a reviewer load is redistributed, or a stale-context issue is stopped before more work lands on it?