Unknown state creates uncertainty
A green process list does not explain whether evidence is current, recovery is ready, or a change is admissible. ACC assembles those signals into one inspectable operating picture.
ACC 1.3.3 · Stable
See what your system knows before you change what it does.
ACC is an engineering control plane for inspecting runtime state, connecting decisions to evidence, and putting explicit checks in front of governed operations. It helps an operator decide what is safe to do next; it does not replace host security, monitoring, or human judgment.
Engineering evidence, not marketing claims
- Architecture validation
- Release verification
- Runtime integrity
- Security foundation
- Open documentation
ACC reduces uncertainty around operational change.
It gives engineers a shared place to inspect state, follow evidence, and apply explicit governance. It does not promise that a system is perfectly safe or make an unsafe host trustworthy.
Fragmented tools weaken context
Monitoring reports symptoms and automation runs work. ACC connects observed state, identity, policy decisions, evidence, and the next governed step without pretending to replace either system.
Uncontrolled change increases risk
ACC keeps analysis, approval, authorization, and execution as separate records. Missing, stale, mismatched, or replayed evidence can stop the protected path instead of being interpreted as consent.
Control that produces engineering outcomes.
ACC 1.3.3 exposes scoped evidence and trust controls. A passing check is never a guarantee about the entire host or system.
Trusted Installation
Fail closed before installer mutation when package authenticity or trust inputs are missing; retain installed identity and footprint evidence.
Outcome: Explicit admission and traceable installation.
Read-only Server Pilot
Admit a least-privilege SSH target with explicit pinned host trust; allow only built-in identity, inventory, and health probes.
Outcome: Bounded observations without arbitrary commands or mutation authority.
Update and Uninstall Boundaries
Inspect safe update readiness and preview evidence. Uninstall remains a non-destructive diagnostic with deletion authority blocked.
Outcome: Readiness does not imply a completed upgrade or removal.
Command Center Dashboard
Run the acc dashboard command to see current state, attention items, available evidence, and the safest next step in that order.
Outcome: A point-in-time operating summary with evidence boundaries.
Access Control
Represent principals, roles, exact permissions, requests, policy evaluations, decisions, and enforcement bindings as separate validated records.
Outcome: An inspectable decision chain instead of a role-name shortcut.
Protected Invocation Identity
Bind one time-bounded, nonce-backed invocation to its authenticated namespace, subject, actor, and principal, then reject expired or replayed identity evidence.
Outcome: Invocation-specific identity evidence, not ambient user trust.
Governed Recovery
Keep recommendation, planning, review, approval, authorization, simulation, attempt, and audit stages explicit; analysis-only records do not grant execution.
Outcome: A reviewable recovery path with deliberate mutation boundaries.
Runtime Evidence
Retain hashes, identifiers, linkage, freshness, and outcomes needed to validate downstream steps and reconstruct material workflows.
Outcome: Traceable records with scoped, testable integrity checks.
Authenticated Release Consumption
Verify package structure and integrity, then explicitly request signature verification with independently trusted signer material before installer admission.
Outcome: A release whose implemented checks can be rerun before installation.
Trust is designed into the way ACC works.
ACC applies a consistent operating philosophy to architecture, security, decisions, and change.
Evidence before action
Consequential action begins with evidence that can be inspected.
Govern before change
Validation and understood impact come before execution.
Every decision is traceable
Context, evidence, ownership, and outcome stay connected.
Architecture is a contract
System structure and behavior are governed, not merely diagrammed.
Security is foundational
Security belongs to the design and operating model from the start.
Deterministic operations
Operations should be predictable, repeatable, inspectable, and recoverable.
A control plane with explicit system boundaries.
ACC separates user entry, platform responsibilities, runtime execution, decision support, infrastructure services, and release lifecycle. Dependency contracts make those boundaries enforceable rather than illustrative.
- CLI
Routes commands and user operations.
- Core
Owns configuration, registry, manifests, documentation, and release.
- Runtime
Coordinates execution, recovery, audit, and authorization.
- Intelligence
Supports decisions, planning, and recommendations.
- Platform
Provides events, history, diagnostics, and security.
- Release
Validates, packages, verifies, and protects release integrity.
Architecture rule: dependencies outside the canonical layer contracts are architecture violations.
Trust the process you can inspect—not a safety slogan.
ACC 1.3.3 binds package identity to readiness evidence. Packaging, certification, mutation, execution and deployment authority remain disabled in the analysis-only readiness record.
- Step 1
Readiness
Canonical version, required entrypoints, architecture policy, regression, manifest consistency, resolver coverage, test registry coverage, and recovery mutation coverage must pass.
- Step 2
Package identity
The archive embeds its release report, manifest, readiness record, version, source commit, and clean-source identity.
- Step 3
Independent verification
The verifier checks structure, identity, readiness and integrity. Explicit authenticity options add signature verification against independently trusted signer material.
- Step 4
Operator decision
A verified result means those implemented checks agree. The operator still evaluates the host, download channel, dependencies, configuration, and deployment context.
Recorded GA evidence: ACC 1.3.3, status READY, source d55e48c. Authenticated release artifacts are publicly available, while signer trust remains independently established.Review verification and trust requirements orreview publication status.
Operational confidence is backed by inspectable controls.
These claims summarize canonical architecture, ACC 1.3.3 GA evidence and scoped security controls; they do not certify a running host.
Runtime integrity is evaluated, not assumed.
The GA report records manifest consistency, resolver coverage, test registry coverage, and recovery mutation coverage as passing analysis checks.
Recorded evidence: Readiness analysis only · no operational authority
A release is the result of repeatable gates.
The 1.3.3 GA report records version, installer and update entrypoints, manifests, architecture, regression and readiness checks as passing.
Recorded evidence: Release 1.3.3: READY · commit d55e48c
Protection is part of the operating model.
The baseline security policy requires secure permissions and enables runtime protection, auditing, integrity verification, and secret protection.
Recorded evidence: Permission Guard · Integrity Guard · Runtime Protection
Product knowledge has an accountable source.
ACC treats documentation as version-controlled product work: one canonical source may support multiple presentations without creating competing technical truth.
Recorded evidence: Documentation as code · version aware · release connected
Don’t take our word for it.
Inspect the controls, evidence, and boundaries yourself.
ACC does not ask a product claim to carry more weight than its evidence. Start with the release record, then inspect the architecture, implemented security model, canonical documentation, and version history. A passing check describes the scope it evaluated—not absolute security, a trusted host, or a correct deployment.
Shared responsibility: ACC can expose state, enforce implemented gates, and preserve evidence. Operators remain responsible for trusted acquisition, host and dependency security, configuration, access, review, deployment context, and the decision to proceed.
CONTROL → INTELLIGENCE → AUTONOMY
ACC is evolving from a governed runtime control system toward an intelligent operational control plane: understand infrastructure state, reason over evidence, recommend safe actions, and coordinate operations under explicit governance.
- ControlShipped in 1.3.3
ACC 1.x
Observe & govern
Establish explicit state, evidence, authority, and safe operating boundaries.
- IntelligenceExploring
Future direction
Understand & decide
Extend evidence-aware control across infrastructure while keeping recommendations inspectable and governed.
- AutonomyVision
Long-term vision
Act & recover
Progressively coordinate complex operations under explicit risk, approval, execution, and verification gates.
Product boundary: the Control capabilities marked “Shipped in 1.3.3” describe the current release. The bounded read-only server pilot is available; broader Intelligence and Autonomy describe direction, not current behavior or an entitlement included in today’s package.
Explore the roadmapChoose the operating model—not a deliberately weakened product.
Proposed edition direction alongside ACC 1.3.3. Prices, server limits and future capabilities below are planning information, not purchasable release entitlements.
Community
$0
No trial expiration
Up to 10 managed servers
Understand · Diagnose · Verify · Safely control
Professional
$49 / month
or $490 / year
Up to 50 managed servers
Automate · Coordinate · Analyze · Recover
Enterprise
Custom pricing
Scope and support aligned to your environment
50+ managed servers · custom scale
Govern · Scale · Integrate · Assure
Useful by default. Sustainable by design.
The ACC team intentionally keeps important, high-impact capabilities in Community. It is not a trial, a fake dashboard, or security crippleware. Paid editions earn their place through scale and additional operational value; foundational security is not a paywall.
Availability note: this is an edition model and commercial direction. Capabilities described elsewhere as future roadmap work are not shipped in ACC 1.3.3 merely because they are assigned to an edition. A possible $29/month founding customer launch offer remains under consideration and is not part of a purchase offer.
Choose the path that matches what you need to prove next.
ACC documentation is version-controlled product knowledge. Start with adoption guidance, inspect the engineering model, or move to a release whose package and integrity evidence can be evaluated together.
Move from orientation to a first governed run.
Follow the getting-started guidance in order so installation, the CLI, and the first runtime interaction share the same versioned context.
Get StartedInspect the system before adopting it.
Use the documentation gateway to review ACC architecture, runtime responsibilities, security controls, release behavior, and CLI guidance from canonical sources.
Read DocumentationChoose a release with its evidence attached.
Start from the download experience for the package, SHA-256 checksum, manifest, release notes, and version-matched installation guidance.
View DownloadA concise path from release guidance to first verification.
- ConfirmReview system requirements and the guidance for the current ACC version.
- InstallUse the documented installer flow instead of an unverified package source.
- VerifyConfirm the installed version and complete the documented first-run checks.
Install from a release record, not from an isolated artifact.
ACC 1.3.3 records the release package, manifest, SHA-256 integrity evidence, and verification gates as part of one release model. Review those records before using the installation path. Authenticated release artifacts are publicly available; authenticated installation still requires independent trust inputs.
Recorded release: version 1.3.3 · commit d55e48c · status READY
Get Started
Start with the guidance that matches the release.
Use the getting-started path for a guided first run, or inspect the canonical documentation before you install.