Architecture overview · pinned public source

How work stays connected

A local board coordinates tasks. Cloud model context crosses a provider boundary.

Seneschal system overviewThe local board coordinates prerequisite sessions and selected access policies, preserves history and sends required context to the chosen provider while a supervisor reviews results.LOCAL WORKSPACEPROVIDER BOUNDARYSELECTSSESSIONACCESSRESULTRETAINSWorkspace & boardA plan becomes visible tasksSelected prerequisitesAll selected dependencies finishTask sessionOpenCode / task contextAccess policyPlan / Build / selected accessReview completed workAccept or request changesLocal historySaved board / linked sessionsSelected model providerRequired prompt and contextSolid: coordination · Dashed: correction requestTeaching overview · no agents or providers run here

Scope and sources

Prerequisites, configured access, retained sessions and supervisor review keep work connected. Provider context is not necessarily local. This overview omits optional bridges, model selection internals, retries and updating.