Pergamum Pulse
Pergamum Pulse is the Constitutional Intelligence Layer of the Viroway ecosystem — the regulatory intelligence and knowledge repository that ZAYAZ, Ask ZARA, and EcoWorld Academy learn from.
It is deliberately not a knowledge base of documents. Pulse stores constitutional knowledge objects: structured, versioned, confidence-scored units of regulatory meaning that machines can reason over and humans can audit.
What a knowledge object is
Every object in Pulse carries three things:
1. Derivation chain
Each interpretation traces its lineage explicitly:
ESRS → Disclosure Requirement → Interpretation
Nothing floats free. When a client-facing answer cites a rule, the chain back to the source standard is machine-resolvable.
2. Authority ladder
Sources are ranked by normative weight, so conflicting guidance resolves deterministically:
- Legislation
- Court rulings
- Regulatory guidance
- Academic research
- Best practice
- Implementation patterns
- Industry examples
3. Confidence and version history
Every object carries a confidence rating and a full version history. When EFRAG revises guidance, the old interpretation isn't overwritten — it's superseded, with the supersession recorded.
The three-tier model
Pulse is organised as constitution / case law / intelligence:
| Tier | Contains | Change mechanism |
|---|---|---|
| Constitution | Ratified normative content — standards, ratified interpretations | Human-ratified amendment flow only |
| Case law | Precedents: how requirements have been interpreted and applied in practice | Accumulates from reviewed real-world application |
| Intelligence | Fresh signal: regulatory news, drafts, consultations, emerging practice | Continuous ingestion (EFRAG first) |
Content is promoted upward — intelligence hardens into case law, case law can be ratified into the constitution — never silently. Amendments to the constitutional tier require human ratification.
What Pulse does for ZAYAZ
Knowledge backbone for Ask ZARA
ZARA answers are grounded in Pulse objects rather than raw retrieval. Because objects carry derivation chains and authority rankings, ZARA's answers are citable, rankable, and auditable — a materially different trust posture from generic RAG.
Note: Internal documents describing the functionality of ZAYAZ and Ecoworld are not stored in Pulse, but in the Docusaurus Manual (specs.zayaz.io). It is however, still part of the RAG system that Ask ZARA gets its information from.
Regulatory intelligence feed (RIF)
Phase 1 ingestion scrapes authoritative sources — EFRAG first — for ESRS developments. ZAYAZ surfaces this as regulatory intelligence: what changed, what it derives from, and which client obligations it touches.
Example of Framework: SBTi corpus and engineified tooling
SBTi methodology, criteria, and guidance documents are ingested into the corpus. Beyond ingestion, the SBTi target-setting tools are being formified and engineified — rebuilt as guided forms plus a calculation engine inside ZAYAZ/Gatehouse. Clients can choose whether to submit targets for validation; the portal supports consultant multi-user access (no public submission API).
Assurance support for Gatehouse (TrustGate)
TrustGate's assurance logic can reference constitutional objects directly: when an assurance check flags a disclosure, the justification resolves to a ratified interpretation with a known authority ranking — not an opinion.
Diagnostic thought partner
A persona-led diagnostic extension (modelled on the Real Change Partner pattern) guides sustainability leaders through structured sessions ending in a written action plan. It lives in two places:
- A free standalone taste as a marketing instrument
- Deep inside ZAYAZ, where sessions draw on what Viroway already knows about the client (COP/IKP context) to produce genuinely tailored plans
Standalone EcoWorld Academy feature
Pulse doubles as an EcoWorld Academy product in its own right — regulatory intelligence for learners and practitioners — with an institutional pricing strategy planned.
Authoring model
All Pulse documentation is authored as MDX with structured frontmatter. The frontmatter is not decorative: it is the machine-readable contract that tells ZARA and downstream tools how each document may be used, cited, and adopted (per the hybrid flat/Frontmatter9 schema).
Architecture direction
- Graph-native storage: planned migration to Neo4j, because derivation chains, authority ladders, and cross-references are inherently graph-shaped
- Phased backend build: Viktor builds from a phased spec, starting with the EFRAG scraping/ingestion pipeline
- Ecosystem position: Pulse sits beneath ZARA, TrustGate, and the Academy as the single constitutional source all three consult
Draft for review. Frontmatter values marked TBD to be filled at ratification; status advances draft → ratified via the amendment flow.