Back to Safora

Safora product guide

Public product guideCurrent reference

The public contract for design-system ingestion, evidence-backed audits, reviewable fixes and re-audits.

The closed loop

  1. Connect sources. Safora can ingest a GitHub repository, Figma source or public documentation URL when that source is enabled for the organization.
  2. Build a Knowledge Pack. Ingestion normalizes source material into typed design-system entities and keeps source evidence for review.
  3. Run an audit. Safora evaluates the selected repository and commit against the active Knowledge Pack.
  4. Review findings and fixes. Eligible findings can produce a branch and pull request. A person still reviews and merges the change.
  5. Run a re-audit. Scores and finding status change only after a completed audit of the updated code.

Knowledge Pack

A Knowledge Pack is the versioned design-system input used by Safora. It contains structured foundations, components, patterns, rules and source references instead of relying on a fixed list of Markdown files.

An AI-ready pack exposes a validated ai-ready.0.1 artifact with an immutable content digest. Consumers can use the typed artifact and its evidence links to distinguish extracted facts from inferred or missing information.

Source coverage and confidence remain visible after generation. A pack can therefore be useful while still identifying gaps that need a human decision or another ingestion pass.

Delivery modes

Every current Knowledge Pack declares how canonical components reach a target repository. That declaration controls which fixes are safe to generate.

package
The canonical component is provided by a named package. Safora verifies the target dependency before proposing an import.
copy-in-repo
The canonical implementation lives in the target repository at a declared path.
external
The pack is documentary only. Safora does not invent an import or component replacement when no deliverable implementation exists.

GitHub commands

The guarded public command surface is deliberately small. Availability also depends on repository access and organization feature settings.

  • @safora audit requests an audit for the current pull request.
  • @safora pause pauses Safora on that repository for 24 hours.
  • @safora resume removes the repository pause.

Safety model

  • Generated changes use a Safora branch and pull request; the default branch is not pushed directly.
  • Safora does not auto-merge generated pull requests.
  • Fix generation can be skipped when delivery, repository context or validation is insufficient.
  • Organization writes are restricted by role; members have read-only access to protected operations.
  • Provider processing, retention and user rights are documented in the Privacy Policy.

Read the current Terms of Service, Privacy Policy and Refund Policy.