Make it big, make it ugly, understand it, refine it, shrink it, polish it.
I think I'm at step 2
Make it big, make it ugly, understand it, refine it, shrink it, polish it.
I think I'm at step 2
CML-> HTML (compat layer) -> Engram
Engram -> Server -> Browser as HTML that directly represents CML
But most importantly, this is loading from an Engram directly on my file system
CML-> HTML (compat layer) -> Engram
Engram -> Server -> Browser as HTML that directly represents CML
But most importantly, this is loading from an Engram directly on my file system
Some amazing news, the Engram Specification is open source and therefore allows for diverse adoption, as well as open governance.
github.com/Manifest-Hum...
Some amazing news, the Engram Specification is open source and therefore allows for diverse adoption, as well as open governance.
github.com/Manifest-Hum...
A universal, read-only archive format that merges a database, a filesystem, and a ZIP into one addressable file.
Data becomes portable, queryable, and eternal.
Specs. SDKs. Performance. Let’s talk 👇
A universal, read-only archive format that merges a database, a filesystem, and a ZIP into one addressable file.
Data becomes portable, queryable, and eternal.
Specs. SDKs. Performance. Let’s talk 👇
The maximum upper size of a single Engram should be ~500GB.
That gives us:
- Documents: 500k-1M
- Internal Index: 5-10GB
- Content: 490-495GB
- Query time: 100-400ms
The maximum upper size of a single Engram should be ~500GB.
That gives us:
- Documents: 500k-1M
- Internal Index: 5-10GB
- Content: 490-495GB
- Query time: 100-400ms
The senate has been working, so this is not about the shutdown.
It is about avoiding a vote to release the Epstein files.