
Symbols and Relations • Layers of Abstraction • Emergence • Mental Architecture building @arsumbrisai
Europe
Joined October 2018
- Tweets889
- Following282
- Followers1.4K
- Likes2.3K
{ I N P U T } retweeted
Build apps on top of your files
a substrate and surface to think in
capture and structure your knowledge
expand on it
build custom apps
and own it all
this is exactly why we are building @arsumbrisai
{ I N P U T } retweeted
knowledge and code bases can get too complex to take in all at once
so you work with shadows: projections and abstractions that reveal different aspects of the same structure
learning to shape those shadows and move between them is an art
Imagine a lab released a model that performs 1:1 like the average human across the board.
Would be such a down grade
{ I N P U T } retweeted
a workspace and framework to build domain-specific systems for agentic knowledge work
local-first, typed markdown and yaml (early alpha) @arsumbrisai
github.com/arsumbris/arsumbr…
{ I N P U T } retweeted
excited to share a walkthrough of @arsumbrisai
build knowledge bases in typed markdown with your agents via mcp, then build your own apps and plugins on top of it
everything lives in repos you can share and extend. a bit like packages for knowledge work
{ I N P U T } retweeted
okay hear me out: an agent framework that operates on top of composable repos, with a type engine that reads them as one typed graph
thats the substrate
repos are like packages for knowledge and the capabilities for working with it
you can package your knowledge together with the skills and mcp tools your agents use to work on it
the ui components also live there
the app is a shell that renders views on top of your substrate
and those views are themselves defined in the substrate, through the same type system
so you and your agent can work on your knowledge AND build the environment you use to work with it
say youre building your company brain in there
your customer notes and deal history already live in the graph
you dont want to pay for a separate crm system when the data is already there
so you and your agent build a crm on top of that data, right inside the same app
e.g. a view of your sales pipeline, with each deal linked to the customer and the conversations behind it
you can also share that view together with the types and agent workflows it needs to let them use your setup (but not necessarily your data)
so someone else brings the repo into their workspace and uses it with their own company data
technical overview of @arsumbrisai
- many repos of md + yaml → one typed graph
- type refinements, cross-repo types
- lists, tuples, inline vs [[linked::repo]] refs
- abstract, sealed, unions, intersections
- typed md bodies, location rules, meta
- au-host: views as typed projections
- au-mcp: tools/hooks/skills as typed plugins
technical overview of @arsumbrisai
- many repos of md + yaml → one typed graph
- type refinements, cross-repo types
- lists, tuples, inline vs [[linked::repo]] refs
- abstract, sealed, unions, intersections
- typed md bodies, location rules, meta
- au-host: views as typed projections
- au-mcp: tools/hooks/skills as typed plugins

















