I added it to the calendar subscription as an invitation, but I cannot edit it directly. It is visible on my end as an awaiting invitation, but please let me know if something it didn’t come through.
@Rola
It worked for me. Can you create the same one for this week (tomorrow)? In addition, it would be helpful if you could do the social media advertisement.
Agent demo: Reiss demonstrated the Systerrae agent’s core capabilities: IOC tracking via provenance graph with incident lineage, auditing framework upload and gap analysis (the agent evaluates coverage across services, policies, and IOCs), knowledge base ingestion from web sources and file uploads, and adaptive workflows that tailor recommendations based on assumed user roles (e.g., wallet provider). Discussion touched on data sanitization needs and plans for transitioning to a web application architecture.
Provenance graph architecture: Currently deployed on a local web server simulating information sharing. The plan is to move to the Begin central server with per-node access control.
Information sharing direction: Integrate a spell book mechanism to support structured information sharing and provenance/knowledge graph construction across sectors.
BGIN Agent: Block 14 Interface (Mitchell)
Mitchell presented the redesigned interface. Key components:
Onboarding & privacy: ECB2 key ceremony (full attribution or anonymous), privacy budget limiting queries to 16 per session, and MyTerms Agreement for machine-readable privacy preferences including AI training consent.
Spell Book (three-graph architecture): Knowledge graph, promise graph, and emergent trust graph. Participants submit documents → the agent analyzes them through a WG-specific lens and casts results to the spell book → information fractures across finance, security, and governance contexts. Relevance/resonance scoring notifies users of related content.
Per-WG agents: Four “mages” (IKP, Finance, Cybersecurity, Governance) each with WG-specific knowledge bases. Moving toward separate knowledge graphs, LLMs, and episodic memory versioned per block, leveraging Bonfire’s system for contributor tracking and idea provenance.
Multilingual Support
50–60% of Block 14 participants are Japanese speakers. A quick test showed promising Japanese I/O results. The proposed approach is a fifth translator agent handling Japanese, French, etc., so the knowledge graph itself remains language-agnostic.
Action Items & Timeline
Shohei: Follow up with Mitchell on minimum viable setup for the Block 14 demo.
Mitchell (this week): Create a Bonfire agent + Telegram bot for each of the four WGs; work with WG chairs to update knowledge bases.
Team (two weeks): Fork the Begin framework into a cybersecurity-specific threat modeling version, maintaining interoperability with the public forum version. Code is on Git.
Next meeting: Monday, same time slot (8am, EST). Block 14 is ~1.5 weeks away.