fluid-core/SCOPE.md
tegwick 82becd0fda Register with State Hub and align workplan IDs to FLUID-WP prefix
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014KmVxhJ35tCo7rE7UnLwWu

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 1116572@bnt-lap001
Assistant-Session: 8ba9bb93-a72a-4883-b189-2499cce5c400
2026-09-04 01:50:34 +02:00

753 B

SCOPE

This file was generated by statehub register. Refine it as the repository boundaries become clearer.

One-liner

Core framework for fluid interfaces to provide adaptive robust systems capability integration.

Core Idea

fluid-core exists to provide the capability described in INTENT.md.

In Scope

  • Maintain the repository's primary implementation.
  • Keep docs, tests, and operational metadata current.

Out of Scope

  • Own unrelated adjacent systems.
  • Make irreversible operational decisions without human approval.

Current State

  • Status: active; implementation and stability should be verified by the repo agent.

Getting Oriented

  • Start with: INTENT.md
  • Agent instructions: AGENTS.md
  • Workplans: workplans/