Projects, presence and sessions issue #5 closed: completed andymccall opened this · 1 comment
andymccall set labels feature ·
andymccall set milestone Sprint 1 ·
andymccall edited ·
andymccall edited ·
andymccall referenced by change 2fc88a7b3a5c on main ·
Done: spectra project add PATH reads .oxy/id, the remote and .oxymodules; relations are derived both ways whichever project is registered first (checked on the real oxygen, oxygenflow, oxygenhub and spectra: hub pins flow, flow pins oxygen, spectra pins oxygen). spectra project list shows pins, pinned-by and agents; agent add refuses an unregistered project. Presence (online, busy, idle, blocked, paused, offline) and sessions (new after ten minutes' silence or on brief(new_session)) are trackers in spectra-core that emit agent.presence and agent.session_started/ended on change; the daemon feeds them in issue #7. agent list shows presence. The 10,000-event harness found that a malformed payload made a projection fail the whole append: projections now skip what they cannot use, and identity and agent tables take only signed events.
andymccall closed ·
Where agents work, and whether they are there (spec §8.1, §8.2, §23.1). Agent creation and ownership are issue #4; this is everything around them.
spectra project add PATH [--name N] [--remote URL]andlist: reads.oxy/for the repository id and the hub remote, and.oxymodulesfordepends_onrelations to other registered projects.spectra agent listanddisable, showing each agent's owner, key, delegation scope and expiry, and project.agent.presenceevents;statustext is self-reported and shown as such.brief(new_session: true), a ULID in every result's_metaand on events.Done when
oxygenandoxygenhubare registered as projects with their relation read from.oxymodules, and an agent's presence moves through its states in a test. After issue #4.