Living Markdown + VFS
Messy property inputs become structured, agent-readable Markdown and virtual files.
Buena + Qontext flagship
Context Surgeon turns scattered property-management data into living Markdown and VFS context, then keeps it current without overwriting the work humans already fixed.
Living VFS
agent-readable property memory
Fact Patch
refresh context without erasing edits
Agent Check
know when it is safe to act
The context layer agents were missing
Leases change. Vendors update terms. Owners override defaults. Agents keep acting on yesterday’s facts unless the context layer is rebuilt with intent.
Messy property inputs become structured, agent-readable Markdown and virtual files.
Every claim carries a quote, source span, confidence score, and conflict status.
Generated context refreshes at fact level while human edits stay intact.
Hackathon sample-data run
The supplied dataset spans CRM, HR, enterprise mail, support, policy PDFs, IT tickets, GitHub, social data, and order PDFs. Context Surgeon compiles it into a file system, graph, review queue, and patchable update layer.
What the judges need to see
We start with raw company state, produce an inspectable VFS plus graph, preserve fact-level provenance, and involve humans only where ambiguity matters.
context-surgeon://inazuma.co/compile
Raw dataset -> VFS -> graph -> human review -> Fact Patch
Raw company state
Top source domains by volume
HR
96,884employees.json · resume_information.csv
CRM
14,951customers.json · products.json · sales.json
Product Sentiment
13,510product_sentiment.json
Enterprise Mail
11,928emails.json
Inazuma Overflow
10,823overflow.json
Collaboration
2,897conversations.json
Entities
9
Edges
8
Provenance
fact span
Updates
Fact Patch
Static memory
3 files
Customers, employees, products, vendors, orders.
Procedural memory
1 file
Policy PDFs, rules, security, SDLC, leave policy.
Trajectory memory
3 files
Tickets, mail, GitHub, collaboration, support progress.
Generated repository files
source-linked/company/inazuma/context.md
Company Operating Context
Dense executive context for AI agents and humans.
/company/inazuma/static/customers.md
Customers and Revenue
Static customer, product, sales, and order memory.
/company/inazuma/static/employees.md
Employees and Roles
Employee directory, HR relationships, resumes, ownership references.
/company/inazuma/procedures/policies.md
Policy Repository
Procedural company rules from policy PDFs.
/company/inazuma/trajectory/projects.md
Projects and Progress
Trajectory memory from mail, collaboration, GitHub, support, and IT tickets.
Maintained by Fact Patch
fact -> source record -> source file/path -> quote/span. New or changed records update the right files without destructive regeneration.
01
Starts with company data, not an agent.
02
Produces a virtual file system plus graph.
03
Preserves references inside files and back to source records.
04
Separates static, procedural, and trajectory knowledge.
05
Uses human review only where ambiguity matters.
06
Optimizes for long-term maintainability by humans and machines.
Recording mode
Sign in only when you want saved workspace state, live source connections, and protected exports.
Demo workbench
Load source material, compile context, preserve a human note, ingest new evidence, apply a Fact Patch, and watch the agent action plan change.
Recording path
Four clicks tell the full Fact Patch story.
Preserved
human note remains untouched
Patched
only stale generated facts change
Changed
agent plan flips to cited action
Audit timeline
Live intake available
The recording path stays focused on the provided demo data. Live mode can still sync Gmail, CRM, files, support, collaboration, work tracking, and manual uploads.
Buena hard problem
Pioneer/Fastino classifies sources before extraction so irrelevant emails do not pollute `context.md` or downstream agent plans.
Partner technologies
Gemini
structured reasoning, conflict explanation, agent pre-flight
Tavily
external enrichment and verification for public/vendor context
Pioneer
schema-first source relevance and extraction pre-pass
001_tenant_roof_leak.txt · 1c7d2bb4
Signal classifier decision
Tenant reports active water ingress, status, and a response deadline for Sonnenallee 44.
classifier: pioneer-fastino-mock
From: Klara Hoffmann <klara.hoffmann@example.de> To: property-manager@hausmail.de Subject: Dachleck in Wohnung 4B weiterhin offen Date: 20 Apr 2026 Objekt: Sonnenallee 44, 12045 Berlin. The roof leak above unit 4B is still open. Water marks expanded after the weekend rain and the tenant asks for a status update by 22 Apr 2026. Please do not mark this as resolved until the ceiling is dry.
Extracted from this source
Agent pre-flight delta
40
before patch
80
after patch
Persisted audit events
Sonnenallee 44 loaded
workspace.loadedPublic preview loaded the bundled property archive.
Sponsor-native architecture
Gemini handles structured reasoning, Tavily enriches and verifies external evidence, Pioneer/Fastino supplies schema-first extraction hints, and the Qontext export makes the property memory inspectable by humans and agents.
Sources
emails, PDFs, CSVs, handover notes
Pioneer pre-pass
document kind + likely entities
Gemini extraction
typed facts + source quotes
Conflict engine
stale, missing, contradictory context
Fact Patch
minimal markdown diff with preserved human edits
Agent check
safe action plan with citations