Agent Server Redesign

Consistency with HM proto + IPFS

User goal: see the exact signed agent+context that led to agent comments+changes

Generic Storage + Permission System

IPFS - Agent server wants to save arbitrary data and specify the permission policy for this.

Generic Resource Concept with Permissions + Schema

Maybe requires a daemon plugin system so that it understands different resource behaviors.

Or, maybe we ship the daemon IPFS data+permission system as a go library?

Linking system- use regular https links to agent server. Suggested by Burdi

Another framing: moving agent memory here, does this behave like a new "git" impl

New Hierarchal Document Permissions system should incorporate these ideas!

Frontend does not push caps?

To what extent does the daemon need to understand schemas?

Does it validate schemas?

Daemon can dynamically run code for interpreting/validating/indexing custom data types.

Schema permanent data: how should it work??

Is inevitable?

If we host arbitrary applications inside seed, we are an OS

HM Redesign

Whats the latest version of a Address = OwnerId + PATH Unified generation system