Foixar — Product

Foixar.Buildfrom idea to sealed, approved work

Scenario Canvas

Model the scenario before anyone writes a ticket.

Actors, triggers, outcomes, and guardrails on a shared canvas — the conversation a whiteboard hosts, with an ending a whiteboard can't deliver: a generated spec.

Grounded targets — pin the scenario to a real application and it checks itself against 619 chunks of your code Guardrails are first-class — constraints travel into the spec, not into a forgotten comment Ready means ready — generation unlocks only when the scenario is complete

Scenario Canvas · month-end close2 of 6 ready

ActorOps analyst

TriggerClose period starts

GuardrailNo posting w/o audit log

Ready2 / 6

Feature Studio

Specs reviewed and sealed — before code exists.

A requirement becomes a spec, stories, and a change boundary grounded in your codebase. Three signals tell everyone exactly where it stands — and an architect signs off before a line is generated.

Three honest signals — machine detection stays frozen; evidence coverage moves as humans refine Business view and engineering view — the BA sees plain-language change areas; the engineer sees governed paths One click to ADO — approved specs become work items and a feature branch

Feature Studio · Global Statisticsarchitect-approved

Detectionfrozen at scan Evidencelive · recalculates Architect-approved

src/app/statistics/grid.component.ts0.82

src/app/statistics/stats.service.ts0.74

src/app/layout/admin.guard.ts0.61

boundary sealed · receipt Δ f04b7a · 16 items → ADO

Foixar.Governrules that actually block

Code Guard · PR Governance

Twenty-eight rules on every pull request.

Foixar's governed registry, the starter packs you forked, and your own tenant rules — evaluated together on every PR, in Azure DevOps or GitHub. Blockers block. Everything else annotates.

Three rule layers — registry, forked starters, and your rules, with clear provenance on each Override with intent — suppress or tighten any rule for your tenant, on the record Merge gates, not suggestions — required checks in your repo host, receipt attached

PR #482 · checksgoverned

Out-of-slice write ARCH-001within boundary

No raw SQL fintech-no-raw-sqlblocked @ L214

Tenant filter on every query fintech✓

Test evidence cited TEST-0013 tests

28 rules · 1 blocker caught · receipt Δ f04b7a on the PR

Marketplace

Start from a domain that's already been burned.

Fintech, healthcare, retail, SaaS — versioned starter packs of rules and decisions hardened by real incidents. Fork at an immutable version; upgrades are always an explicit, reviewable diff.

Immutable forks — publisher updates never change your tenant silently Versioned lineage — see exactly what v1.1.0 changed, and why it promoted a rule to blocker

Marketplace · starter fingerprints

v1.1.0Fintech · .NETFintech — .NET Core API9 rules · 8 blockers · 3 ADR

v1.0.0Healthcare · AngularHealthcare — Angular Portal7 rules · 1 ADR · upgrade available

forks are frozen at fork time · upgrades are explicit

Foixar.Intelligenceinstitutional memory, on the record

Decision Memory · Ask Foixar

The "why" survives the person who decided it.

Every architectural decision is captured with provenance — who, when, from which conversation — and cited back automatically the next time it's relevant, whether that's in a spec, a PR, or a question in Teams.

Captured in the flow — decisions land from Feature Studio Q&A, imports, or Ask Foixar, not a separate chore Answers, grounded — ask in Teams or Slack, get plain-language answers with sources attached

Decision Memory · ADR-014

Active

All payment traffic routes through the API gateway

Direct provider calls are forbidden from client apps. Decided after the March incident review; supersedes the 2024 direct-integration pattern.

Feature Studio · step-4 Q&A cited on PR #482 receipt Δ 8c41f2

asked about 4× this quarter · answered from memory every time

Audit Trail

Every verdict, every receipt, forever on file.

Pass, recorded, or fail — each governance verdict lands in a tenant-wide ledger with its full receipt chain: sealed context → artifacts → run → evidence. Built for the day compliance, a client, or an underwriter asks.

Why it failed, in one click — every fail links to the rule, the line, and the sealed boundary it violated Evidence that leaves with you — stored in your Blob and your repos, admissible without us in the room

Audit Trail · last 30 days

41 pass232 recorded23 fail

write outside sealed boundary — refusedΔ b2e19c · 2:09 PM

generation approved · 28 rules passΔ f04b7a · 11:32 AM

receipt chain: context → artifacts → run → evidence

Canvas→Spec→ADO / GitHub→Code→Governed PR→Receipt— one pipeline, shared context at every step

Everything between the idea and the merge.