Evidence Engine

Ask about Seditio, describe a project, or try to make it say something untrue. Every answer is built from cited, verbatim passages of seditio.ie and checked before you see it.

The engine runs instantly in your browser: rule-based retrieval over seditio.ie, with no language model.

F13 ↓

Ask · Brief · Challenge

Try it

Ready · Instant engine in your browser · no AI model needed

How modes work

Instant engine: runs in your browser, instantly. It retrieves, ranks and verifies passages of seditio.ie with deterministic rules; no language model writes text.

Live AI: not available on this deployment.

Read the privacy notice

Type a question (up to 400 characters)

Try to break it →

Examples recorded when this page was built

Example answer

Example produced by the instant engine when this page was built · 15 November 2026 · corpus 8c2bc00d

How do you keep humans in control of AI agents?

Engine: Here's what seditio.ie says:

Clear Talent's Ava assistant supports goal, KPI and review workflows while keeping approval and evidence handling under human control.

Seditio begins with the decision or task to improve, then engineers the surrounding product, data, evaluation and human controls.

Human control: Review, approval and escalation

Evaluation and human-approval controls

5 stages · 7.8 ms measured at build · 0 model calls

Example brief

Example produced by the instant engine when this page was built · 15 November 2026 · corpus 8c2bc00d

What the engine read

A multi-tenant SaaS for property managers: tenants report issues, pay bills online, and use QR codes to open doors and lifts.

  • SaaS product
  • Property management
  • Payments
  • Devices and IoT

How your needs map to published work

Match map: 4 requirements, 4 capabilities, 5 evidence items
RequirementMatched capabilityEvidence
SaaS product Custom SaaS Development · SaaS Platform Modernization ManagedPMO (Strong match) · How much does custom SaaS development cost? · SaaS architecture checklist for a growing platform
Property management Custom SaaS Development · SaaS Platform Modernization · React Native App Development · Mobile App Development ManagedPMO (Strong match) · How much does custom SaaS development cost? · SaaS architecture checklist for a growing platform · ZoomRPM (Partial match)
Payments Custom SaaS Development ManagedPMO (Strong match) · How much does custom SaaS development cost?
Devices and IoT React Native App Development · Mobile App Development ManagedPMO (Strong match) · ZoomRPM (Partial match)

Reference architecture sketch

Assembled by fixed rules from your description. Components not marked BY RULE come from words you used, highlighted above. Components marked BY RULE were added by a rule because of something you described; they aren't in your words. Each component shows Seditio's published evidence or guidance for that kind of part.

Reference architecture sketch · from your description

Example produced by the instant engine when this page was built · 15 November 2026 · corpus 8c2bc00d

Rule-based reference architecture · not a design, estimate or quote

Instant engine · runs in your browser · no AI model neededSignals: rules in your browser · Composition: rules@sketch-2.0.0 · No language model

Skip the sketch list
  1. Experience

    1. Web applicationYour words: "multi-tenant" · Case study: ManagedPMO

      Typical role (generic, not a description of the evidence below)

      A browser-based interface for the system's users, on desktop and mobile screens.

      Why it's on this sketch

      • Your words: "multi-tenant" (SaaS product, found by a rule in your browser)
      • Your words: "SaaS" (SaaS product, found by a rule in your browser)

      Rule SK-T-01 places it when your description includes any of: SaaS product, Customer or partner portal (narrowed by SK-R4: not only "dashboard"), Marketplace, Booking or scheduling.

      Seditio evidence

      Case study: ManagedPMO

      Progressive web application for field workflows

      ManagedPMO › Documented impactSource unit: work:managedpmo#impact.1

      The ManagedPMO case study says the platform was developed with RoboMo. It doesn't say which parts Seditio built.

      Seditio's published guidance (not evidence of delivery)

      Web application development turns business rules and user journeys into browser-based software.

      Web Application Development › OverviewSource unit: service:web-application-development#overview.2

      Connections

      • Sends to: Application services — Interfaces call the application services.

      Sends to: Application services

  2. Identity & tenancy

    1. Sign-in and permissionsBY RULEBy rule SK-T-07 · Guidance only

      Typical role (generic, not a description of the evidence below)

      Confirms who each user is and controls what each role can see and do.

      Why it's on this sketch

      • BY RULE: added by rule SK-T-07 because your description includes Several customer organisations ("multi-tenant"). This component isn't named in your description.
      • BY RULE: added by rule SK-T-07 because your description includes SaaS product ("multi-tenant"). This component isn't named in your description.

      Rule SK-T-07 adds it when your description includes any of: SaaS product, Customer or partner portal (narrowed by SK-R4: not only "dashboard"), Marketplace, Several customer organisations, Health data, Financial data, Children's data.

      Seditio evidence

      Not described in a published Seditio case study.

      Seditio's published guidance (not evidence of delivery)

      Identity and tenancy

      Document how users join organisations, hold multiple roles, move between tenants and recover access.

      SaaS architecture checklist for a growing platform › Identity and tenancySource unit: insight:saas-architecture-checklist#section-2.0

      Connections

      • Receives from: Application services — Application services check who the user is and what they may do.

    2. Tenant isolationYour words: "multi-tenant" · Guidance only

      Typical role (generic, not a description of the evidence below)

      Keeps each customer organisation's users and data separate inside one shared system.

      Why it's on this sketch

      • Your words: "multi-tenant" (Several customer organisations, found by a rule in your browser)

      Rule SK-T-08 places it when your description includes any of: Several customer organisations.

      Seditio evidence

      Not described in a published Seditio case study.

      Seditio's published guidance (not evidence of delivery)

      Identity and tenancy

      Every data query and background job must preserve tenant boundaries.

      SaaS architecture checklist for a growing platform › Identity and tenancySource unit: insight:saas-architecture-checklist#section-2.1

      Connections

  3. Core services

    1. Application servicesBY RULEBy rule SK-T-09 · Case study: ManagedPMO

      Typical role (generic, not a description of the evidence below)

      Server-side logic that holds the business rules.

      Why it's on this sketch

      • BY RULE: added by rule SK-T-09 because your description includes SaaS product ("multi-tenant"). This component isn't named in your description.
      • BY RULE: added by rule SK-T-09 because your description includes Payments ("pay bills"). This component isn't named in your description.

      Rule SK-T-09 adds it when your description includes any of: SaaS product, Customer or partner portal, Marketplace, Booking or scheduling, Internal tool, Mobile app, Field or on-site work, Reporting and dashboards, Workflow automation, Approvals and human review, Answers from your documents, AI assistant or chat, AI agent (narrowed by SK-R2), Document extraction (narrowed by SK-R5), Ranking or matching (narrowed by SK-R3), Summaries and drafting, Devices and IoT, Payments (narrowed by SK-R1).

      Seditio evidence

      Case study: ManagedPMO

      Developed with RoboMo, ManagedPMO introduced tenant issue workflows, utility records, online bill payment and IoT-linked access using QR scanners and elevator relay controllers.

      ManagedPMO › The solutionSource unit: work:managedpmo#solution.0

      The ManagedPMO case study says the platform was developed with RoboMo. It doesn't say which parts Seditio built.

      Seditio's published guidance (not evidence of delivery)

      Seditio designs the user experience, architecture, backend, APIs and operating model as one connected system.

      Custom Software Development › OverviewSource unit: service:custom-software-development#overview.3

      Connections

      • Receives from: Web application — Interfaces call the application services.

      • Sends to: Sign-in and permissions — Application services check who the user is and what they may do.

      • Sends to: Tenant isolation — Every request is scoped to one customer organisation.

        Identity and tenancy

        Every data query and background job must preserve tenant boundaries.

        SaaS architecture checklist for a growing platform › Identity and tenancySource unit: insight:saas-architecture-checklist#section-2.1

      • Sends to: Operational database — Application services read and write the records.

      • Sends to: Background jobs and retries — Slow or failure-prone work is handed to background jobs.

      • Sends to: Payments — Payment requests come from the application.

      • Receives from: Device and IoT connections — Device readings and events reach the application.

      Sends to: Sign-in and permissions, Tenant isolation, Operational database, Background jobs and retries, Payments

    2. Background jobs and retriesBY RULEBy rule SK-T-11 · Guidance only

      Typical role (generic, not a description of the evidence below)

      Runs slow or failure-prone work outside the user's request and retries it when it fails.

      Why it's on this sketch

      • BY RULE: added by rule SK-T-11 because your description includes SaaS product ("multi-tenant"). This component isn't named in your description.
      • BY RULE: added by rule SK-T-11 because your description includes Payments ("pay bills"). This component isn't named in your description.

      Rule SK-T-11 adds it when your description includes any of: (SaaS product, Customer or partner portal, Marketplace, Booking or scheduling, Internal tool, Mobile app, Field or on-site work, Reporting and dashboards, Workflow automation, Approvals and human review, Answers from your documents, AI assistant or chat, AI agent (narrowed by SK-R2), Document extraction (narrowed by SK-R5), Ranking or matching (narrowed by SK-R3), Summaries and drafting, Devices and IoT, Payments (narrowed by SK-R1)) together with any of (CRM integration, Helpdesk or ticketing, ERP or accounting system, EHR or clinical records, Payments (narrowed by SK-R1), Email, E-commerce, a system you named (not hosting, analytics or sign-in), Devices and IoT, AI agent (narrowed by SK-R2), Document extraction (narrowed by SK-R5)).

      Seditio evidence

      Not described in a published Seditio case study.

      Seditio's published guidance (not evidence of delivery)

      Data and integrations

      Webhook retries and dead-letter handling

      SaaS architecture checklist for a growing platform › Data and integrationsSource unit: insight:saas-architecture-checklist#section-3.6

      Connections

      • Receives from: Application services — Slow or failure-prone work is handed to background jobs.

      • Sends to: Integration layer — Background work exchanges data with other systems.

        Data and integrations

        Choose authoritative systems, idempotent integration patterns and recovery procedures.

        SaaS architecture checklist for a growing platform › Data and integrationsSource unit: insight:saas-architecture-checklist#section-3.0

      Sends to: Integration layer

    3. PaymentsYour words: "pay bills" · Case study: ManagedPMO · Same passage as Application services

      Typical role (generic, not a description of the evidence below)

      Takes payments through a payment provider and records each outcome against the right account.

      Why it's on this sketch

      • Your words: "pay bills" (Payments, found by a rule in your browser)

      Rule SK-T-13 places it when your description includes any of: Payments (narrowed by SK-R1).

      Seditio evidence

      Case study: ManagedPMO

      Developed with RoboMo, ManagedPMO introduced tenant issue workflows, utility records, online bill payment and IoT-linked access using QR scanners and elevator relay controllers.

      ManagedPMO › The solutionSource unit: work:managedpmo#solution.0

      The ManagedPMO case study says the platform was developed with RoboMo. It doesn't say which parts Seditio built.

      Same passage as Application services

      Connections

      • Receives from: Application services — Payment requests come from the application.

  4. Integration

    1. Device and IoT connectionsYour words: "QR codes" · Case study: ManagedPMO

      Typical role (generic, not a description of the evidence below)

      Receives readings or events from physical devices and can send commands to them.

      Why it's on this sketch

      • Your words: "QR codes" (Devices and IoT, found by a rule in your browser)
      • Your words: "open doors" (Devices and IoT, found by a rule in your browser)
      • +1 more places in your description

      Rule SK-T-17 places it when your description includes any of: Devices and IoT.

      Seditio evidence

      Case study: ManagedPMO

      Integrated software with IoT access devices

      ManagedPMO › Documented impactSource unit: work:managedpmo#impact.2

      The ManagedPMO case study says the platform was developed with RoboMo. It doesn't say which parts Seditio built.

      Connections

      • Sends to: Application services — Device readings and events reach the application.

      Sends to: Application services

    2. Integration layerBY RULEBy rule SK-T-14 · Case study: Pixreview

      Typical role (generic, not a description of the evidence below)

      The part of the system that exchanges data with other systems' APIs.

      Why it's on this sketch

      • BY RULE: added by rule SK-T-14 because your description includes Payments ("pay bills"). This component isn't named in your description.

      Rule SK-T-14 adds it when your description includes any of: CRM integration, Helpdesk or ticketing, ERP or accounting system, EHR or clinical records, Payments (narrowed by SK-R1), Email, E-commerce, a system you named (not hosting, analytics or sign-in), Existing or legacy system.

      Seditio evidence

      Case study: Pixreview

      Integrated multiple review and communications APIs

      Pixreview › Documented impactSource unit: work:pixreview#impact.2

      Seditio's published guidance (not evidence of delivery)

      Data and integrations

      Choose authoritative systems, idempotent integration patterns and recovery procedures.

      SaaS architecture checklist for a growing platform › Data and integrationsSource unit: insight:saas-architecture-checklist#section-3.0

      Connections

  5. Data

    1. Operational databaseBY RULEBy rule SK-T-19 · Guidance only

      Typical role (generic, not a description of the evidence below)

      Stores the application's records.

      Why it's on this sketch

      • BY RULE: added by rule SK-T-19 because your description includes SaaS product ("multi-tenant"). This component isn't named in your description.
      • BY RULE: added by rule SK-T-19 because your description includes Payments ("pay bills"). This component isn't named in your description.

      Rule SK-T-19 adds it when your description includes any of: SaaS product, Customer or partner portal, Marketplace, Booking or scheduling, Internal tool, Mobile app, Field or on-site work, Reporting and dashboards, Workflow automation, Approvals and human review, Answers from your documents, AI assistant or chat, AI agent (narrowed by SK-R2), Document extraction (narrowed by SK-R5), Ranking or matching (narrowed by SK-R3), Summaries and drafting, Devices and IoT, Payments (narrowed by SK-R1).

      Seditio evidence

      Not described in a published Seditio case study.

      Seditio's published guidance (not evidence of delivery)

      Seditio designs the interface, backend, data model and integrations as one coherent system.

      Web Application Development › OverviewSource unit: service:web-application-development#overview.3

      Connections

      • Receives from: Application services — Application services read and write the records.

  6. Baseline practices (not from your description)

    Shown on every sketch because Seditio's published guidance lists them. Quoted, not paraphrased.

    1. Automated deployment and monitoringBASELINECase study: ManagedPMO

      Typical role (generic, not a description of the evidence below)

      Builds, tests and releases each change automatically, watches the running system and supports rolling back a bad release.

      Seditio's published guidance (not evidence of delivery)

      Delivery and operations

      A growing SaaS needs automated deployment, observability, security updates and capacity signals.

      SaaS architecture checklist for a growing platform › Delivery and operationsSource unit: insight:saas-architecture-checklist#section-4.0

      Delivery and operations

      The team should know how to detect an incident, roll back and communicate before the first major customer arrives.

      SaaS architecture checklist for a growing platform › Delivery and operationsSource unit: insight:saas-architecture-checklist#section-4.1

      Seditio evidence

      Case study: ManagedPMO

      Designed for continuous cloud deployment

      ManagedPMO › Documented impactSource unit: work:managedpmo#impact.3

      The ManagedPMO case study says the platform was developed with RoboMo. It doesn't say which parts Seditio built.

    2. Backups and tested recoveryBASELINEGuidance only

      Typical role (generic, not a description of the evidence below)

      Regular backups of data and configuration, with restores rehearsed so recovery is known to work.

      Seditio's published guidance (not evidence of delivery)

      Data and integrations

      Backups and tested recovery

      SaaS architecture checklist for a growing platform › Data and integrationsSource unit: insight:saas-architecture-checklist#section-3.4

      Seditio evidence

      Not described in a published Seditio case study.

Composed by fixed rules from a catalogue of 30 generic components. Components marked BY RULE were added by rules, not by your words. It doesn't choose vendors, size anything, set a timeline or price, and it isn't a proposal. Treat it as a checklist for a first conversation, not a plan.
Why a sketch and not a design?

A design needs decisions this page can't make: who your users are, what your data rules are, what you already run, and what you can operate after launch. The engine only knows the words you typed.

So the sketch is assembled by rules from a fixed catalogue. A component appears when words in your description name it, or when a rule adds it because of something you described; rule-added components are marked BY RULE. Each one shows Seditio's published case-study evidence for that kind of part where it exists, and says so where it doesn't.

It never names vendors, sizes, phases, durations or costs. Seditio's cost guide explains why:

Treat any instant estimate without those distinctions as a sales number, not a delivery plan.

How much does custom SaaS development cost? › The useful answer is a range tied to risk

Closest published evidence

A cloud property-management platform, developed with RoboMo, that joins tenant workflows, online bill payment, utility records and IoT-linked access.

Cross-device app

Matching capabilities, guides and industries (8)

Multi-tenant application architecture

In stages behind stable interfaces: new components run alongside old ones, traffic or tenants move over gradually, and each step has a tested rollback.

Seditio's portfolio includes cross-device healthcare, property and performance-management experiences backed by integrated cloud platforms.

ZoomRPM includes a cross-device patient application, while ManagedPMO supports mobile property workflows and IoT-connected access processes.

A focused internal workflow can be substantially smaller than a regulated multi-tenant platform with billing, mobile access and third-party data.

Define the customer, tenant, user, subscription, data ownership and service commitments before choosing cloud services.

A focused SaaS MVP usually takes roughly three to six months from the start of discovery to launch: days to a few weeks of discovery, two to four weeks of experience and architecture design, eight to sixteen weeks of engineering and one to three weeks of UAT and launch.

Utility and billing records

What will drive cost

  • Not flagged from your description Product uncertainty: how much discovery and validation is still required
  • Flagged Workflow and permission complexity
  • Flagged External systems and data migration
  • Not flagged from your description Security, compliance and audit requirements
  • Not flagged from your description Service expectations after launch

Published timeline guidance

Typical ranges from Seditio's published guidance — not an estimate for your project.

  • Discovery and scope: usually days to a few weeks
  • Experience and architecture design: often two to four weeks
  • Focused MVP engineering: commonly eight to sixteen weeks
  • UAT and launch: typically one to three weeks
  • Continuous product improvement: ongoing

Questions to settle first

  1. What measurable outcome will show that the first release works?
  2. Which systems must it integrate with, and who controls access to them?
  3. Which security, compliance and audit requirements apply?
  4. What is the narrowest first release that would still be useful?
  5. Who will support and operate it after launch, and with what service expectations?
  6. How do customer organisations, tenants and users relate, and who owns each tenant's data?
Five stages

How it works

Stages use the five steps Seditio publishes for applied AI. Each lists the engine steps that ran under it.

  1. 01

    Business signal

    L0 normalise → PII redaction → L1 screen → planner (intent, answer type, tokens)

  2. 02

    Trusted context

    typed lookups (company facts) and/or 5-channel retrieval → RRF → rerank → diversity

  3. 03

    Model + tools

    offline: extractive composer (no model)

  4. 04

    Human control

    output rules over every sentence; approval gate for enquiries

  5. 05

    Measured outcome

    timings, usage, cost; CTA selection

Fig. 13 — How the Evidence Engine runs

Business signal

Trusted context

Model + tools

Human control

Measured outcome

Business signal

  • → feeds Hygiene & PII redaction

  • → feeds Rule screen

  • → feeds Classifier screen, Planner

  • → feeds Planner

  • → feeds 5 retrieval channels

Trusted context

  • → feeds 5 retrieval channels, Publication guard (checks every page)

  • → feeds Rank fusion & rerank

  • → feeds Offline composer (rules), Language-model answerer

Model + tools

  • → feeds Output rules

  • → feeds Output rules

Human control

  • → feeds Model check of each sentence, Trace & cost

  • → feeds Trace & cost

  • → feeds Trace & cost

Measured outcome

  • → feeds Trace & cost

Your question or description

The text you type. No visitor text ever appears in URLs.

Module src/engine/kernel/index.ts

Hygiene & PII redaction

NFKC, zero-width and bidi strip, HTML strip, caps, PII redaction. PII redaction is applied before anything else sees the text.

Module src/engine/core/policy/pii.ts

Rule screen

Deterministic rules with spans. Declines, boundaries and pricing make no model call.

Module src/engine/core/policy/input-rules.ts

Classifier screen (live only — not configured on this deployment)

In live mode, a classifier scores the current question for injection, comparison, claim-probe and pricing intent. It can only route to a deterministic template.

Module src/engine/server/screen.ts

Planner

Intent, answer type and tokens. Corrections, substitutions and expansions are listed in the trace.

Module src/engine/core/retrieve/planner.ts

Corpus built from seditio.ie content at deploy

Citable units come from typed view-models (the same functions the templates render), never from DOM textContent. kb-verify proves every unit appears verbatim on its page.

Module scripts/engine/build-corpus.ts

5 retrieval channels

Typed lookups (company facts) and/or 5-channel retrieval. Every candidate section is listed in the retrieval table.

Module src/engine/core/retrieve/channels.ts

Rank fusion & rerank

RRF → rerank → diversity. The trace shows per-channel ranks, RRF and rerank features.

Module src/engine/core/retrieve/rerank.ts

Offline composer (rules)

Extractive composer, no model. Quotes are corpus text only.

Module src/engine/core/compose/answer.ts

Language-model answerer (live only — not configured on this deployment)

Writes Ask answers as sentences that cite passage handles, under a strict JSON schema. Earlier questions never reach a model.

Module src/engine/server/answer.ts

Output rules

The rules run per sentence. Offline they run over template strings plus quotes as a self-check, and must always pass.

Module src/engine/core/verify/rules.ts

Model check of each sentence (live only — not configured on this deployment)

Checks that each sentence is supported by the passages it cites, before any text is shown. Support probability is not a measure of truth.

Module src/engine/server/judge.ts

Your approval (enquiries)

The engine can't send messages. Nothing is sent until you approve the draft.

Module src/engine/ui/ApprovalCard.tsx

Trace & cost

Every number comes from an event. Nothing is estimated, except cost, which is labelled as an estimate.

Module src/engine/ui/TracePanel.tsx

CI evaluation

Evaluation uses a dev split for tuning and a held-out test split written by non-engineers. The held-out test split does not exist yet; held-out results will be published when the independent test set is complete.

Module scripts/engine/eval.ts

Publication guard (checks every page)

Runs DENY_LIST and CERTIFICATION_SCOPE on every built page. This step fails the build if any page publishes a claim Seditio has chosen not to make.

Module scripts/engine/publication-guard.ts

View as list
  1. Business signal
    • Your question or description: The text you type. No visitor text ever appears in URLs. → feeds Hygiene & PII redaction
    • Hygiene & PII redaction: NFKC, zero-width and bidi strip, HTML strip, caps, PII redaction. PII redaction is applied before anything else sees the text. → feeds Rule screen
    • Rule screen: Deterministic rules with spans. Declines, boundaries and pricing make no model call. → feeds Classifier screen (live only — not configured on this deployment), Planner
    • Classifier screen (live only — not configured on this deployment): In live mode, a classifier scores the current question for injection, comparison, claim-probe and pricing intent. It can only route to a deterministic template. → feeds Planner (live only — not configured on this deployment)
    • Planner: Intent, answer type and tokens. Corrections, substitutions and expansions are listed in the trace. → feeds 5 retrieval channels
  2. Trusted context
    • Corpus built from seditio.ie content at deploy: Citable units come from typed view-models (the same functions the templates render), never from DOM textContent. kb-verify proves every unit appears verbatim on its page. → feeds 5 retrieval channels, Publication guard (checks every page)
    • 5 retrieval channels: Typed lookups (company facts) and/or 5-channel retrieval. Every candidate section is listed in the retrieval table. → feeds Rank fusion & rerank
    • Rank fusion & rerank: RRF → rerank → diversity. The trace shows per-channel ranks, RRF and rerank features. → feeds Offline composer (rules), Language-model answerer (live only — not configured on this deployment)
  3. Model + tools
    • Offline composer (rules): Extractive composer, no model. Quotes are corpus text only. → feeds Output rules
    • Language-model answerer (live only — not configured on this deployment): Writes Ask answers as sentences that cite passage handles, under a strict JSON schema. Earlier questions never reach a model. → feeds Output rules (live only — not configured on this deployment)
  4. Human control
    • Output rules: The rules run per sentence. Offline they run over template strings plus quotes as a self-check, and must always pass. → feeds Model check of each sentence (live only — not configured on this deployment), Trace & cost
    • Model check of each sentence (live only — not configured on this deployment): Checks that each sentence is supported by the passages it cites, before any text is shown. Support probability is not a measure of truth. → feeds Trace & cost (live only — not configured on this deployment)
    • Your approval (enquiries): The engine can't send messages. Nothing is sent until you approve the draft. → feeds Trace & cost
  5. Measured outcome
    • Trace & cost: Every number comes from an event. Nothing is estimated, except cost, which is labelled as an estimate.
    • CI evaluation: Evaluation uses a dev split for tuning and a held-out test split written by non-engineers. The held-out test split does not exist yet; held-out results will be published when the independent test set is complete. → feeds Trace & cost
    • Publication guard (checks every page): Runs DENY_LIST and CERTIFICATION_SCOPE on every built page. This step fails the build if any page publishes a claim Seditio has chosen not to make.
Lanes are the five published stages. Select a step to see what it does and where its code lives.
Refusals

What it will not do

Prices are never produced, along with day rates, estimates, delivery dates, headcount, client counts, retention figures, awards and company-level certifications. Durations appear only as verbatim published ranges marked “not an estimate for your project”.

  • Rule PRICE.rate
    Template pricing-approach/v1

    seditio.ie publishes indicative budget bands, not quotes or rates. It explains how cost is driven by scope and risk.

  • Rule CLAIM.cert
    Template claim-boundary/cert

    seditio.ie doesn't state that Seditio Group holds certifications. What it does publish on the topic is project-specific.

  • Rule CLAIM.scale
    Template claim-boundary/scale

    seditio.ie doesn't publish headcount, client-count or project-count figures. For team shape and availability, ask the team directly.

  • Rule CLAIM.retention
    Template claim-boundary/retention

    seditio.ie doesn't publish retention, satisfaction or success-rate figures.

  • Rule CLAIM.awards
    Template claim-boundary/awards

    seditio.ie doesn't publish awards, rankings, ratings or testimonials.

  • Rule CLAIM.guarantee
    Template claim-boundary/guarantee

    seditio.ie doesn't publish delivery guarantees or service terms. Terms are agreed per engagement.

  • Rule CMP.competitor
    Template decline/comparison

    The engine doesn't compare Seditio with other companies.

  • Rule OOS.*
    Template decline/out-of-scope

    That's outside what this engine does. It answers questions about Seditio using seditio.ie.

  • Rule INJ.*
    Template decline/injection

    This engine only answers questions about Seditio from what's published on seditio.ie, and its rules can't be changed from the question box. The exact prompts and rules are published on this page.

  • No thinking display, fake streaming, staggers or animated replays.
  • No visitor text ever appears in URLs.
  • Removed text never crosses the wire, except in Challenge mode, where it is labelled.
Publication guard

The same verifier checks this website

Two of the output rules that check every sentence the engine shows, DENY_LIST and CERTIFICATION_SCOPE, also run in CI over every page of the site, llms.txt and the Organization JSON-LD. The build fails if any of them publishes a claim that Seditio has chosen not to make.

Publication guard
  1. CI
  2. Build
  3. Pages Every built HTML page, llms.txt, llms-full.txt and Organization JSON-LD
  4. Publication guard DENY_LIST and CERTIFICATION_SCOPE on every page Fail
  5. Deploy
  • It runs DENY_LIST and CERTIFICATION_SCOPE (with the page's subject entity) on every page, and SUPERLATIVE as a warning only.
  • This step fails the build if any page publishes a claim Seditio has chosen not to make.
  • Citable units come from typed view-models (the same functions the templates render), never from DOM textContent. kb-verify proves every unit appears verbatim on its page.

One rule set is private: a list of specific claims Seditio has decided not to publish. It runs in CI and on the server and is never sent to browsers, because publishing it would publish those claims.

Methodology

Evaluation

Evaluation uses a dev split for tuning and a held-out test split written by non-engineers. Only test-split numbers are published, rendered from CI JSON. The held-out test split does not exist yet, so this section publishes the methodology; held-out results will be published when the independent test set is complete.

What is measured for each published evaluation dimension
DimensionOffline metric (every build)
Factual grounding and citationsCitation validity: share of rendered sentences mapping to units. Output rule violations. kb-verify coverage.
Task completion qualityTest split: section R@1, R@5, MRR@8, template accuracy; Brief: top-3 precision, strength accuracy
Unsafe or out-of-scope responsesRed-team catch rate; false-positive rate; decline accuracy
Latency and cost per successful taskWorker p50 / p95 run ms (Node)
Escalation and correction rateShare routed to contact or abstain

Rows: How to integrate AI into an existing SaaS product › Ground and evaluate

Evaluation datasets
SplitAuthorShipped to the browser?
dev (tuning)engineersno
held-out testwritten by Seditio staff who are not engineers, or by the clientno
red-team: injection, claim-probe, PII, exfiltration, out-of-scopeengineers + panel probespublic subset only
false-positive: benign look-alikesengineerspublic subset
brief fixturesengineers, reviewed by a Seditio engineerpublic subset
Verify-a-claimengineerspublic subset

Engineers may not read the cases while tuning; CI prints aggregates only.

Modules and data flow

How this is built

The engine is pure TypeScript in src/engine/core/**, with no DOM and no Node APIs. The same code runs in the browser module worker, the build scripts and CI.

Layers

  1. core (pure TS)
  2. worker (module Web Worker)
  3. kernel (browser singleton)
  4. surfaces
    • strip (vanilla DOM, homepage)
    • console (React island, /evidence-engine)
  5. server (Node) imports core directly; never imports kernel/ui.

The live code path is compiled in but disabled on this deployment.

Embeds outside /evidence-engine are offline only, whatever the live status.

Modules

src/engine/core/
pure TS: schema, text, policy, retrieve, compose, verify, brief, diagram, pipeline
src/engine/worker/
module Web Worker: corpus fetch, index build, every pipeline run
src/engine/kernel/
browser singleton: worker client, reducer, status, hand-offs, analytics
src/engine/ui/
the console on this page (React)
src/engine/strip/
the homepage strip (vanilla DOM)
src/engine/server/
live mode only (Node); never imported by client code

Why no embeddings

  1. Offline mode needs lexical retrieval anyway, so one core serves both modes.
  2. A second retrieval stack (embedding calls at build and query time, plus vector storage) isn't justified for about 28K tokens of first-party text.
  3. In-browser embedding models cost tens of MB.
  4. Section-level citations and an inspectable retrieval table matter more here than semantic recall.

Privacy

With the Instant engine, nothing leaves your browser.

Read the privacy notice

Costs

The Instant engine costs $0 to run.

Published rules

Read the prompts and rules

Regexes are layer 1 of N. Every sentence the engine shows is checked by the output rules, whatever L1 catches.

Defences, in layers
Prompt-injection defences, in layers
LayerMechanismOffline
L0 Input hygieneNFKC, zero-width and bidi strip, HTML strip, caps, PII redaction✓
L1 ScreenDeterministic rules with spans. Declines, boundaries and pricing make no model call.✓
L3 Trust boundaryVisitor text in tagged, escaped data blocks; evidence only as handle-labelled passages; published instructions; earlier questions never reach a model; no tools✓ (no model)
L4 Generation limitsOffline: extractive composer. Live: strict JSON schema; citations restricted to a handle enum; server-enforced sentence, citation and word limits; no reasoning; store: false✓
L5 Output verificationThe deterministic rules, then the private deny list (server only), then the judge, then the strict keep policyrules
L6 Rendering safetyQuotes are corpus text only✓
L7 Action gateNothing is sent until you approve the draft✓
Input rules (L1 screen)
L1 screen rules: matched case-insensitively over the normalised text; precedence injection > pii > out-of-scope > comparison > claim-probe > pricing > in-scope
Rule idClassPattern (summary, word-bounded)ActionModel call
INJ.overrideinjection(ignore|disregard|forget|override|bypass)\b.{0,40}\b(instruction|prompt|rule|guardrail|polic|what came before|everything above|previous|prior|above); \bnew (task|instructions?)\s*:; from now on\bdecline decline/injectionNo
INJ.personainjectionyou are now, act as, pretend (to be|you), role-?play, developer mode, jailbreak, \bDAN\b, respond only asdeclineNo
INJ.exfilinjectionsystem prompt, your (instructions|rules|prompt), hidden prompt, repeat (the|everything) (text )?above, print .{0,20}(prompt|instructions)decline + link to the published prompt (#prompts)No
INJ.markupinjection</?(system|assistant|user|visitor_question|tool)[^>]*>, \[/?INST\], triple-backtick system, <!--declineNo
INJ.encodedinjectionbase64 run ≥ 80 chars, \\u[0-9a-f]{4} sequences ≥ 10declineNo
PII.*pii(L0 redactions occurred)redact-and-continue + noteafter redaction
OOS.creativeout-of-scope\b(poem|song|joke|story|recipe|weather|horoscope|lyrics)\bdecline decline/out-of-scopeNo
OOS.codeout-of-scope\b(write|debug|fix|generate)\b.{0,30}\b(code|script|regex|sql|function|scraper|program)\bdeclineNo
OOS.taskout-of-scope^(translate|summari[sz]e|rewrite|paraphrase)\b (task verbs aimed at arbitrary text)declineNo
CMP.competitorcomparison(better|cheaper|faster|worse) than, \bvs\.?\b, compared? (to|with) + agency/company nounsdecline decline/comparison + pinned /insights/choose-software-development-partnerNo
CLAIM.certclaim-probe(iso ?\d{4,5}|soc ?2|pci|hipaa|gdpr|cyber essentials) + (certif|accredit|complian|audit|attest)claim-boundary/certNo
CLAIM.scaleclaim-probehow (many|big|large) + (employees|engineers|developers|staff|people|clients|customers|projects|integrations); headcount; team sizeclaim-boundary/scaleNo
CLAIM.retentionclaim-proberetention|churn|satisfaction|nps|success rate|track recordclaim-boundary/retentionNo
CLAIM.awardsclaim-probeawards?|award-winning|ranked|top \d+|#1|number one|testimonials?|clutch|ratings?|(client|customer) reviews|reviews? (on|from); (are you|is seditio) the best (a bare "review" does not match, so "review process" and "code review" are safe)claim-boundary/awardsNo
CLAIM.guaranteeclaim-probeguarantee|refund|warranty|money-back|slaclaim-boundary/guaranteeNo
PRICE.ratepricingprice|pricing|cost|costs|quote|budget|hourly|(day|daily|hourly) rates?|your rates?|how much|fees?|charge|per (sprint|hour|day|month)|retainer (a bare "rate" does not match, so "conversion rate" and "success rate" don't route here)pricing-approach/v1No
Output rules
Output rules, run per sentence: offline over template strings and quotes as a self-check, live before the judge, and in CI over page text
Rule idFires whenLive action
LINK_POLICYURL, markdown link or image, or an HTML tag in the sentenceremove sentence
NO_CITATIONSentence has factual content (a digit or number word, a known entity, Seditio as subject, a cert term, or a claim verb) and no citation. Connectives of ≤ 12 words with none of these are allowed.remove
UNSUPPORTED_NUMBERA numeral, number word, N+ or percentage is absent from the union of the sentence's cited unit texts and the visitor question (normalised: strip thousands separators and trailing punctuation; number words → numerals)remove
CERTIFICATION_SCOPEA cert term plus a cert verb (certif*, accredit*, complian*, audit*, maintain*, hold*, attest*), where the sentence subject ≠ the subject of the cited unit containing the termremove
COMPANY_CLAIM_UNSUPPORTEDSubject is Seditio (Seditio, Seditio Group, the company, its team, they/it after a Seditio subject) and the predicate is a past result (built, delivered, supported, achieved, processed, worked with, has … for) or a quantity/quality claim (retains, every, all clients, always) but there's no cited unit of kind claim or faqremove
POSITIONING_AS_EVIDENCEA past-result sentence cites only positioning unitsremove
UNKNOWN_ENTITYA multi-word Title Case n-gram or a known brand (a dictionary of about 300 common company and product names) not found in the entity registry, the aliases, the cited text or the visitor questionremove
SUPERLATIVEbest, leading, top-tier, world-class, best-in-class, #1, number one, award-winning, unrivalled, unmatched, guaranteed, cutting-edge, trusted by absent from the cited textremove
PRICE_FIGUREA currency symbol or code + digits, \d+k, per (hour|day|sprint|month) with a numberremove
TESTIMONIAL_FORMA quoted statement attributed to a person or role (" … " — CTO)remove
DENY_LISTServer and CI only. Private patterns. The UI shows the id DENY_LIST without the pattern.remove

One rule set is private: a list of specific claims Seditio has decided not to publish. It runs in CI and on the server and is never sent to browsers, because publishing it would publish those claims.

FAQ

Questions

Is this a chatbot?

No. It's a retrieval and verification system over seditio.ie. It has no persona, it doesn't chat, and it only answers from published passages, with citations.

Does it use AI?

The offline engine uses deterministic retrieval, ranking and rule-based verification, with no language model.

Why won't it give me a price?

A price depends on scope the engine cannot see, so it never produces a figure for your project. Seditio publishes indicative budget bands, not quotes or rates, and its cost guide explains why a quick estimate without that scope is “a sales number, not a delivery plan”. The engine shows the published cost drivers instead and lets you send a brief to the team.

Why does it sometimes say the site doesn't cover something?

Because it doesn't. The engine is built to say so rather than guess.

Can Seditio build something like this for my product?

This engine uses the same disciplines Seditio applies to client AI systems: grounding, permissions, evaluation and cost control.

Work with the team that built this

Talk to the engineers behind the Evidence Engine.

Grounding, verification, evaluation and cost control are the same disciplines Seditio applies to client AI systems.