AI products · Local prototype

OwnStack

Adapt software without handing over authority.

A local software-adaptation studio that separates model proposals from host-enforced permissions, exact human approval, verification and rollback.

OwnStack local prototype interface
Project screenshot

Screenshot · local prototype · synthetic data

The question

Customer-specific changes should not silently become cross-tenant access or unreviewed code changes. A proposed action needs a precise scope and an accountable decision.

How it works

  • Route requests to a declared capability, engineering review or refusal; retain authorization in the host.
  • Bind approval to an exact proposal and enforce tenant/project scope, expiry, revocation and stale-result fencing.
  • Persist requests and outbox events, export linked evidence, and preserve failed model drafts for inspection.

Evidence & results

  • Local synthetic-tenant workflows record approved access, cross-tenant denial and revocation.
  • Stored PostgreSQL/HTTP fault scenarios exercise interruption and recovery with a synthetic provider.
  • A saved local SQL lookup comparison improved the large-history case but regressed on the one-grant workload.

Scope & next steps

  • Local reference system, without a verified customer pilot or production security review.
  • Recorded live model patch attempts failed; the passing manual recovery fixture is not a successful model-generated patch.
  • Local lookup timing is not HTTP capacity or a production latency result.

Go one level deeper.

Ask about the implementation, tradeoffs, or my contribution.

Explore with the portfolio guide