Establish fluid-core scaffold, intent, and phased workplans

Adds the repository structure, INTENT.md declaring the wire-contract
boundary, and seven workplans covering Blueprint Phases A-C plus the
fluid-telegram handover.

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
This commit is contained in:
tegwick 2026-09-04 01:49:12 +02:00
parent af4bf798c4
commit c2cfe86d88
15 changed files with 5712 additions and 0 deletions

View file

@ -0,0 +1,14 @@
Fluid interfaces is a framework to establish a dynamic adaptive interface between services
that integrates self healing and self optimization based on interface telemetrie.
FLUID stands for FlowUtilizingInterfaceDaemon.
The idea is about having an actively developing interface that learns and evolves from mesuring
interface usage and responsibility.
The interface can implent REST, GRAPH or other API flavors and functions as a classic deterministic
API but on error or detection of missing functionality can trigger AI review, planning of the missing
endpoints or endpoint extensions connecting them to backend implementation or even requesting new
backend implementation.