MetacircularDynamics

Metacircular Dynamics ("metacircular") and WNTRMUTE Heavy Industries ("wntrmute") are my two umbrella project names for personal computational services and projects. Observe the following general rules when designing and developing services for either:

1. All service data should go in /srv/<project name> to facilitate moving services between machines.
2. While services should have accompanying systemd unit files, they should be container-first. This facilitates deployment via the MCP (Metacircular Control Plane).
3. Service should use the metacircular identity and access system for user management, general access control, and so forth.
   • The Swagger docs
   • The MCIAS integration documentation
   • Determine whether there is a policy restricting a user (whether by username or role) from accessing auth:login; this indicates that a particular user or role is blacklisted from accessing the system.
   • MCIAS users have associated roles; the admin role should be granted full administrative access to the system, user should be granted full non-administrative access, and guest should be restricted in whatever sense that means for the service. This is a general guideline and service-dependent.
4. Generally, services will have both a gRPC and REST API. The gRPC gateway approach should be taken to keep the REST and gRPC APIs in sync. The web UI should use htmx and provide full functionality over the