Search
1000 results for “quantixed”
-
Building a Local-First Multi-Agent Orchestration Platform
The Problem with Cloud-Centric AI vs Local-First AI Orchestration
The cloud has long been the default stage for artificial intelligence. Frameworks such as LangChain, AutoGen, and CrewAI make it possible to orchestrate local or hosted models. However, their design still leans toward API-based, cloud-first execution. That approach works for experimentation, yet it introduces a clear weakness: dependence.
This return to autonomy echoes the early days of personal computing explored in Riding the Waves: From Home Computers to AI Orchestration, where individual control shaped innovation before the cloud era began.
From cassette tapes and floppy disks to orchestrated AI systems, computing has evolved through every wave.Every remote call carries both cost and exposure. Sensitive data must leave the machine to be processed elsewhere. Token-based billing discourages iteration. Even when using secure endpoints, developers trade autonomy for convenience. As a result, innovation is often limited by infrastructure.
A local-first approach changes that balance. It focuses on privacy, predictability, and cost control by running agents directly on local hardware. The cloud remains useful for large or complex tasks, yet local processing gives developers freedom. It does not reject connectivity; instead, it restores choice.
That principle guided the creation of a production-grade orchestration platform of roughly 3,700 lines of Python. Through seven BDD development cycles and a 96.5 percent test pass rate, it proved that a reliable system can run with zero external dependencies. Using SQLite and JSONL metrics, the same codebase coordinates multiple AI agents securely, predictably, and locally across devices.
Three-Layer Architecture of a Local-First AI Orchestration Platform
The system follows three clear layers: CLI, Orchestrator, and Registry. Each layer handles a specific function in the orchestration lifecycle.
The CLI layer, built with Typer, serves as the command surface. It offers more than twenty commands and about six hundred lines of code. Developers can initialize environments, run agents, and invoke workflows. This layer is the human-facing edge of the platform.
The Orchestrator layer, written with FastAPI, acts as the control center. It manages scheduling, routing, and task lifecycles. Its asynchronous design lets small tasks run in parallel while heavy inference jobs are handled one at a time. The main application file stays compact and easy to read.
The Registry layer defines intelligence. Eleven expert agents are declared in Pydantic configurations that describe capabilities, dependencies, and budgets. New agents can be added or updated with simple configuration changes.
FastAPI was chosen for its async speed and automatic schema generation. SQLite replaced Redis to stay aligned with the local-first approach. JSONL metrics were selected for their simplicity and transparency. As a result, commands call APIs, APIs invoke agents, and agents return results through a steady feedback loop.
These principles align with the broader ethical and security implications discussed in AI Orchestration, Security, and the Future of Work, where resilience and accountability shape the next phase of automation.
Hardware-Aware Resource Scheduling in a Local-First AI Orchestration Platform
Local-first systems must respect hardware limits. Machines differ widely: some are laptops with integrated GPUs, while others are workstation-class servers with up to 128 GB of RAM and powerful GPUs. Consequently, the orchestrator adapts through hardware-aware scheduling.
Each environment selects one of three profiles: Laptop, Workstation; or Server, defined in a simple
resources.yamlfile:profile: workstation max_agent_runs: 4 gpu_memory_limit: 16000 cpu_cores: 8
During initialization, the active profile sets concurrency gates and resource budgets. Lightweight operations run together, while heavy tasks acquire locks before execution. A dual-lock system separates general resource tracking from expensive AI calls. This method maintains parallel work without conflict.
Scheduling moves through five stages: global concurrency check, CPU allocation, GPU budgeting, codex serialization, and cleanup. Each stage keeps the system predictable and stable. Cleanup routines always release resources, even after errors.
This approach brings precision and balance to orchestration rather than experimentation.
Despite these advantages, running a local-first AI orchestration platform introduces its own constraints. The system’s performance depends directly on available hardware, and smaller machines may need to rely on compact or quantized models such as Phi or Llama variants instead of large-scale cloud models. This balance between efficiency and accuracy requires careful model selection. In addition, while workstation-class setups with 128 GB of RAM can handle concurrent agents with ease, laptops or limited servers may experience slower inference or constrained multitasking. These realities remind developers that local-first design is not about matching the cloud’s abundance, but about achieving sustainable autonomy within real hardware boundaries.
Integrating the Model Context Protocol (MCP)
While a local platform values privacy, it still needs secure communication. The Model Context Protocol (MCP) provides structured interoperability for tools that observe or influence AI workflows.
The implementation, only 254 lines of code, supports two authentication modes: simple tokens for development and shared-secret tokens for production. It runs across HTTP, WebSocket, and TCP. As a result, the system remains flexible yet secure.
Through the MCP tool system, external services can register abilities such as
memory.readormemory.write. These allow dashboards, IDEs, or bots to stream workflow events in real time. For example, a Grafana panel can show resource usage, while an IDE plugin can display agent progress.In short, MCP turns a local orchestrator into a cooperative system—connected when needed, private by default.
For a deeper exploration of how MCP enables cross-agent collaboration, see Unlocking AI Collaboration with the Model Context Protocol.
A symbolic visual of the Model Context Protocol: where developer flow, memory, and modular context converge.
DAG-Based Workflow Execution
At its heart, orchestration is dependency management. The platform models workflows as directed acyclic graphs (DAGs), where each node represents a task and edges define dependencies.
A common configuration is:
plan → (backend, frontend) → (security, qa)
The product manager agent drafts a feature plan. Backend and frontend agents work in parallel. Security and QA agents then validate results. Prompts reuse earlier outputs through simple placeholders like
{backend.result}. The queue engine runs each step, stores results, and queues the next tasks until completion.This design preserves context, improves traceability, and supports recovery from partial failure. This emphasis on context-driven execution mirrors insights from AI Agents and Large Codebases: Why Context Beats Speed Every Time.
The Three-Tier Guardrail System
Stable orchestration requires discipline. Therefore, the platform applies a three-tier guardrail system.
- Input validation filters unsafe or malformed prompts.
- Runner control manages retries and captures runtime errors.
- Output checks reject empty or inconsistent responses.
All guardrail events are logged in
guardrail_metrics.jsonlwith categories such asguardrail_block,runner_error, andvalidator_block. Developers can view them directly:python -m agents.cli.main metrics guardrail --details 5
As a result, every failure becomes visible and fixable. Silent issues disappear.
The Eleven Expert Agents
Intelligence resides in the registry of eleven expert agents. They are grouped into development, security, and infrastructure domains.
- Development:
product_manager,bdd_backend,bdd_frontend,qa - Security:
security,validator,guardrail - Infrastructure:
database,networking,web3,encryption
Each agent includes a Pydantic schema defining its role and resource limits. During startup, these definitions convert to runtime specifications. This clear separation keeps the system flexible. Moreover, every action is logged, ensuring full transparency.
Built-In Web Dashboard
Transparency should not require the cloud. Instead, the platform provides a lightweight local web dashboard with seven views: system overview, workflows, guardrails, resources, agent timeline, MCP clients, and JSON API.
Each page loads in under 100 milliseconds and refreshes automatically. It remains responsive, simple, and always available—even offline.
Context Management and Memory
Persistent context keeps intelligence coherent. The SQLite-backed memory system uses two tables:
memoryfor key-value data andhistoryfor append-only logs.Agents use REST or MCP calls to read and write context. This lets long workflows maintain state between runs. As a result, agents can recall past outputs or user preferences without external storage.
Developer Experience and Automation
Starting up is simple:
python -m agents.cli.main init --profile laptop
This single command creates all configuration files, chooses a hardware profile, and prepares directories. The CLI also scaffolds projects in five languages: Python, Go, React, PHP, and Perl. Each uses templates with variable substitution for fast setup.
With more than twenty commands and six sub-apps, Typer provides clear and self-documented interfaces. Consequently, the CLI becomes both toolkit and guide.
A BDD-Driven Development Journey
Development followed seven BDD cycles, each improving a key feature:
- MCP authentication and security
- Zero-friction initialization
- API deduplication
- Resource scheduling
- Dashboard observability
- Advanced resource tracking
- Fail-fast initialization
Each cycle used RED-GREEN-REFACTOR testing and generated living Gherkin documentation. As a result, coverage now exceeds 85 percent, keeping behavior predictable while features evolve.
A visual metaphor of how structured thinking, like Gherkin and Behavior-Driven Development, helps AI systems connect human intent with machine execution.
The importance of clear behavioral documentation aligns closely with ideas from AI, Gherkin, and the Future of Software Development: Why Behavior-Driven Development Matters.Production Readiness and Lessons Learned
The final system demonstrates production-level quality. It includes thread-safe scheduling, clear error handling, and real-time monitoring. JSONL metrics make audits simple. Configuration is idempotent and safe to repeat.
Key technical innovations include:
- Fail-fast error handling with clear fixes
- Append-only metrics for transparency
- Dual-lock control for parallel work
- Hot-swappable agent settings
- Hardware-aware scaling across profiles
Building locally highlighted several truths. Simplicity brings reliability. In addition, insight into system behavior is essential. Developer experience shapes success as much as model accuracy. Above all, privacy and control can align with capability.
The platform now runs seamlessly across laptops, workstations, and servers. Each profile is tuned to its limits, and each agent knows its role.
The Future of Local-First AI Orchestration Platforms
The local-first AI orchestration platform proves that autonomy and performance can coexist. It respects hardware, protects data, and offers hybrid flexibility. In practice, it shows that orchestration can be as private as computation itself. This serves as a foundation for tools that return control to their builders.
Next comes refinement: wider support for edge devices, stronger context management, and closer integration with ecosystems such as Claude CLI and OpenAI APIs. Although the system is already production-grade, its deeper importance lies in the idea it represents: local-first intelligence as a craft, not a slogan.
The cloud will always have its place. However, it should never be the only place. Ultimately, true orchestration begins where control is personal.
The next frontier of AI engineering will not be written in the cloud alone. It will emerge from local workstations, developer labs, and edge devices where privacy and autonomy coexist. If this vision of local-first orchestration resonates with your work or research, share your thoughts, build upon the concept, or join the discussion on how to design systems that respect both hardware and humanity. Real progress begins when we question the defaults and start building differently.
What is a local-first AI orchestration platform?
A local-first AI orchestration platform manages multiple AI agents directly on local hardware instead of relying on cloud APIs. It improves privacy, reduces cost, and increases control over performance.
How does hardware-aware scheduling improve AI orchestration?
It adapts task execution to available resources such as CPU cores and GPU memory, ensuring stability on devices ranging from laptops to 128 GB workstations.
What role does the Model Context Protocol (MCP) play?
MCP enables secure communication between agents and external tools, allowing dashboards and IDEs to interact with workflows in real time while maintaining local control.
Can local-first systems replace cloud orchestration entirely?
Not completely. The cloud remains valuable for large-scale training and inference. Local-first orchestration complements it by offering autonomy, speed, and privacy for smaller or sensitive workflows.Key Takeaways
- A local-first AI orchestration platform enhances autonomy, privacy, and cost control by running AI agents directly on local hardware.
- It features a three-layer architecture: CLI for commands, Orchestrator for task management, and Registry for defining agent intelligence.
- The platform employs hardware-aware scheduling to optimize performance based on device capabilities, such as laptops or servers.
- The Model Context Protocol (MCP) facilitates secure communication between agents and external tools while maintaining local control.
- Its future includes support for edge devices and deeper integration with existing ecosystems, emphasizing personal control over AI workflows.
-
Building a Local-First Multi-Agent Orchestration Platform
The Problem with Cloud-Centric AI vs Local-First AI Orchestration
The cloud has long been the default stage for artificial intelligence. Frameworks such as LangChain, AutoGen, and CrewAI make it possible to orchestrate local or hosted models. However, their design still leans toward API-based, cloud-first execution. That approach works for experimentation, yet it introduces a clear weakness: dependence.
This return to autonomy echoes the early days of personal computing explored in Riding the Waves: From Home Computers to AI Orchestration, where individual control shaped innovation before the cloud era began.
From cassette tapes and floppy disks to orchestrated AI systems, computing has evolved through every wave.Every remote call carries both cost and exposure. Sensitive data must leave the machine to be processed elsewhere. Token-based billing discourages iteration. Even when using secure endpoints, developers trade autonomy for convenience. As a result, innovation is often limited by infrastructure.
A local-first approach changes that balance. It focuses on privacy, predictability, and cost control by running agents directly on local hardware. The cloud remains useful for large or complex tasks, yet local processing gives developers freedom. It does not reject connectivity; instead, it restores choice.
That principle guided the creation of a production-grade orchestration platform of roughly 3,700 lines of Python. Through seven BDD development cycles and a 96.5 percent test pass rate, it proved that a reliable system can run with zero external dependencies. Using SQLite and JSONL metrics, the same codebase coordinates multiple AI agents securely, predictably, and locally across devices.
Three-Layer Architecture of a Local-First AI Orchestration Platform
The system follows three clear layers: CLI, Orchestrator, and Registry. Each layer handles a specific function in the orchestration lifecycle.
The CLI layer, built with Typer, serves as the command surface. It offers more than twenty commands and about six hundred lines of code. Developers can initialize environments, run agents, and invoke workflows. This layer is the human-facing edge of the platform.
The Orchestrator layer, written with FastAPI, acts as the control center. It manages scheduling, routing, and task lifecycles. Its asynchronous design lets small tasks run in parallel while heavy inference jobs are handled one at a time. The main application file stays compact and easy to read.
The Registry layer defines intelligence. Eleven expert agents are declared in Pydantic configurations that describe capabilities, dependencies, and budgets. New agents can be added or updated with simple configuration changes.
FastAPI was chosen for its async speed and automatic schema generation. SQLite replaced Redis to stay aligned with the local-first approach. JSONL metrics were selected for their simplicity and transparency. As a result, commands call APIs, APIs invoke agents, and agents return results through a steady feedback loop.
These principles align with the broader ethical and security implications discussed in AI Orchestration, Security, and the Future of Work, where resilience and accountability shape the next phase of automation.
Hardware-Aware Resource Scheduling in a Local-First AI Orchestration Platform
Local-first systems must respect hardware limits. Machines differ widely: some are laptops with integrated GPUs, while others are workstation-class servers with up to 128 GB of RAM and powerful GPUs. Consequently, the orchestrator adapts through hardware-aware scheduling.
Each environment selects one of three profiles: Laptop, Workstation; or Server, defined in a simple
resources.yamlfile:profile: workstation max_agent_runs: 4 gpu_memory_limit: 16000 cpu_cores: 8
During initialization, the active profile sets concurrency gates and resource budgets. Lightweight operations run together, while heavy tasks acquire locks before execution. A dual-lock system separates general resource tracking from expensive AI calls. This method maintains parallel work without conflict.
Scheduling moves through five stages: global concurrency check, CPU allocation, GPU budgeting, codex serialization, and cleanup. Each stage keeps the system predictable and stable. Cleanup routines always release resources, even after errors.
This approach brings precision and balance to orchestration rather than experimentation.
Despite these advantages, running a local-first AI orchestration platform introduces its own constraints. The system’s performance depends directly on available hardware, and smaller machines may need to rely on compact or quantized models such as Phi or Llama variants instead of large-scale cloud models. This balance between efficiency and accuracy requires careful model selection. In addition, while workstation-class setups with 128 GB of RAM can handle concurrent agents with ease, laptops or limited servers may experience slower inference or constrained multitasking. These realities remind developers that local-first design is not about matching the cloud’s abundance, but about achieving sustainable autonomy within real hardware boundaries.
Integrating the Model Context Protocol (MCP)
While a local platform values privacy, it still needs secure communication. The Model Context Protocol (MCP) provides structured interoperability for tools that observe or influence AI workflows.
The implementation, only 254 lines of code, supports two authentication modes: simple tokens for development and shared-secret tokens for production. It runs across HTTP, WebSocket, and TCP. As a result, the system remains flexible yet secure.
Through the MCP tool system, external services can register abilities such as
memory.readormemory.write. These allow dashboards, IDEs, or bots to stream workflow events in real time. For example, a Grafana panel can show resource usage, while an IDE plugin can display agent progress.In short, MCP turns a local orchestrator into a cooperative system—connected when needed, private by default.
For a deeper exploration of how MCP enables cross-agent collaboration, see Unlocking AI Collaboration with the Model Context Protocol.
A symbolic visual of the Model Context Protocol: where developer flow, memory, and modular context converge.
DAG-Based Workflow Execution
At its heart, orchestration is dependency management. The platform models workflows as directed acyclic graphs (DAGs), where each node represents a task and edges define dependencies.
A common configuration is:
plan → (backend, frontend) → (security, qa)
The product manager agent drafts a feature plan. Backend and frontend agents work in parallel. Security and QA agents then validate results. Prompts reuse earlier outputs through simple placeholders like
{backend.result}. The queue engine runs each step, stores results, and queues the next tasks until completion.This design preserves context, improves traceability, and supports recovery from partial failure. This emphasis on context-driven execution mirrors insights from AI Agents and Large Codebases: Why Context Beats Speed Every Time.
The Three-Tier Guardrail System
Stable orchestration requires discipline. Therefore, the platform applies a three-tier guardrail system.
- Input validation filters unsafe or malformed prompts.
- Runner control manages retries and captures runtime errors.
- Output checks reject empty or inconsistent responses.
All guardrail events are logged in
guardrail_metrics.jsonlwith categories such asguardrail_block,runner_error, andvalidator_block. Developers can view them directly:python -m agents.cli.main metrics guardrail --details 5
As a result, every failure becomes visible and fixable. Silent issues disappear.
The Eleven Expert Agents
Intelligence resides in the registry of eleven expert agents. They are grouped into development, security, and infrastructure domains.
- Development:
product_manager,bdd_backend,bdd_frontend,qa - Security:
security,validator,guardrail - Infrastructure:
database,networking,web3,encryption
Each agent includes a Pydantic schema defining its role and resource limits. During startup, these definitions convert to runtime specifications. This clear separation keeps the system flexible. Moreover, every action is logged, ensuring full transparency.
Built-In Web Dashboard
Transparency should not require the cloud. Instead, the platform provides a lightweight local web dashboard with seven views: system overview, workflows, guardrails, resources, agent timeline, MCP clients, and JSON API.
Each page loads in under 100 milliseconds and refreshes automatically. It remains responsive, simple, and always available—even offline.
Context Management and Memory
Persistent context keeps intelligence coherent. The SQLite-backed memory system uses two tables:
memoryfor key-value data andhistoryfor append-only logs.Agents use REST or MCP calls to read and write context. This lets long workflows maintain state between runs. As a result, agents can recall past outputs or user preferences without external storage.
Developer Experience and Automation
Starting up is simple:
python -m agents.cli.main init --profile laptop
This single command creates all configuration files, chooses a hardware profile, and prepares directories. The CLI also scaffolds projects in five languages: Python, Go, React, PHP, and Perl. Each uses templates with variable substitution for fast setup.
With more than twenty commands and six sub-apps, Typer provides clear and self-documented interfaces. Consequently, the CLI becomes both toolkit and guide.
A BDD-Driven Development Journey
Development followed seven BDD cycles, each improving a key feature:
- MCP authentication and security
- Zero-friction initialization
- API deduplication
- Resource scheduling
- Dashboard observability
- Advanced resource tracking
- Fail-fast initialization
Each cycle used RED-GREEN-REFACTOR testing and generated living Gherkin documentation. As a result, coverage now exceeds 85 percent, keeping behavior predictable while features evolve.
A visual metaphor of how structured thinking, like Gherkin and Behavior-Driven Development, helps AI systems connect human intent with machine execution.
The importance of clear behavioral documentation aligns closely with ideas from AI, Gherkin, and the Future of Software Development: Why Behavior-Driven Development Matters.Production Readiness and Lessons Learned
The final system demonstrates production-level quality. It includes thread-safe scheduling, clear error handling, and real-time monitoring. JSONL metrics make audits simple. Configuration is idempotent and safe to repeat.
Key technical innovations include:
- Fail-fast error handling with clear fixes
- Append-only metrics for transparency
- Dual-lock control for parallel work
- Hot-swappable agent settings
- Hardware-aware scaling across profiles
Building locally highlighted several truths. Simplicity brings reliability. In addition, insight into system behavior is essential. Developer experience shapes success as much as model accuracy. Above all, privacy and control can align with capability.
The platform now runs seamlessly across laptops, workstations, and servers. Each profile is tuned to its limits, and each agent knows its role.
The Future of Local-First AI Orchestration Platforms
The local-first AI orchestration platform proves that autonomy and performance can coexist. It respects hardware, protects data, and offers hybrid flexibility. In practice, it shows that orchestration can be as private as computation itself. This serves as a foundation for tools that return control to their builders.
Next comes refinement: wider support for edge devices, stronger context management, and closer integration with ecosystems such as Claude CLI and OpenAI APIs. Although the system is already production-grade, its deeper importance lies in the idea it represents: local-first intelligence as a craft, not a slogan.
The cloud will always have its place. However, it should never be the only place. Ultimately, true orchestration begins where control is personal.
The next frontier of AI engineering will not be written in the cloud alone. It will emerge from local workstations, developer labs, and edge devices where privacy and autonomy coexist. If this vision of local-first orchestration resonates with your work or research, share your thoughts, build upon the concept, or join the discussion on how to design systems that respect both hardware and humanity. Real progress begins when we question the defaults and start building differently.
What is a local-first AI orchestration platform?
A local-first AI orchestration platform manages multiple AI agents directly on local hardware instead of relying on cloud APIs. It improves privacy, reduces cost, and increases control over performance.
How does hardware-aware scheduling improve AI orchestration?
It adapts task execution to available resources such as CPU cores and GPU memory, ensuring stability on devices ranging from laptops to 128 GB workstations.
What role does the Model Context Protocol (MCP) play?
MCP enables secure communication between agents and external tools, allowing dashboards and IDEs to interact with workflows in real time while maintaining local control.
Can local-first systems replace cloud orchestration entirely?
Not completely. The cloud remains valuable for large-scale training and inference. Local-first orchestration complements it by offering autonomy, speed, and privacy for smaller or sensitive workflows.Key Takeaways
- A local-first AI orchestration platform enhances autonomy, privacy, and cost control by running AI agents directly on local hardware.
- It features a three-layer architecture: CLI for commands, Orchestrator for task management, and Registry for defining agent intelligence.
- The platform employs hardware-aware scheduling to optimize performance based on device capabilities, such as laptops or servers.
- The Model Context Protocol (MCP) facilitates secure communication between agents and external tools while maintaining local control.
- Its future includes support for edge devices and deeper integration with existing ecosystems, emphasizing personal control over AI workflows.
-
Building a Local-First Multi-Agent Orchestration Platform
The Problem with Cloud-Centric AI vs Local-First AI Orchestration
The cloud has long been the default stage for artificial intelligence. Frameworks such as LangChain, AutoGen, and CrewAI make it possible to orchestrate local or hosted models. However, their design still leans toward API-based, cloud-first execution. That approach works for experimentation, yet it introduces a clear weakness: dependence.
This return to autonomy echoes the early days of personal computing explored in Riding the Waves: From Home Computers to AI Orchestration, where individual control shaped innovation before the cloud era began.
From cassette tapes and floppy disks to orchestrated AI systems, computing has evolved through every wave.Every remote call carries both cost and exposure. Sensitive data must leave the machine to be processed elsewhere. Token-based billing discourages iteration. Even when using secure endpoints, developers trade autonomy for convenience. As a result, innovation is often limited by infrastructure.
A local-first approach changes that balance. It focuses on privacy, predictability, and cost control by running agents directly on local hardware. The cloud remains useful for large or complex tasks, yet local processing gives developers freedom. It does not reject connectivity; instead, it restores choice.
That principle guided the creation of a production-grade orchestration platform of roughly 3,700 lines of Python. Through seven BDD development cycles and a 96.5 percent test pass rate, it proved that a reliable system can run with zero external dependencies. Using SQLite and JSONL metrics, the same codebase coordinates multiple AI agents securely, predictably, and locally across devices.
Three-Layer Architecture of a Local-First AI Orchestration Platform
The system follows three clear layers: CLI, Orchestrator, and Registry. Each layer handles a specific function in the orchestration lifecycle.
The CLI layer, built with Typer, serves as the command surface. It offers more than twenty commands and about six hundred lines of code. Developers can initialize environments, run agents, and invoke workflows. This layer is the human-facing edge of the platform.
The Orchestrator layer, written with FastAPI, acts as the control center. It manages scheduling, routing, and task lifecycles. Its asynchronous design lets small tasks run in parallel while heavy inference jobs are handled one at a time. The main application file stays compact and easy to read.
The Registry layer defines intelligence. Eleven expert agents are declared in Pydantic configurations that describe capabilities, dependencies, and budgets. New agents can be added or updated with simple configuration changes.
FastAPI was chosen for its async speed and automatic schema generation. SQLite replaced Redis to stay aligned with the local-first approach. JSONL metrics were selected for their simplicity and transparency. As a result, commands call APIs, APIs invoke agents, and agents return results through a steady feedback loop.
These principles align with the broader ethical and security implications discussed in AI Orchestration, Security, and the Future of Work, where resilience and accountability shape the next phase of automation.
Hardware-Aware Resource Scheduling in a Local-First AI Orchestration Platform
Local-first systems must respect hardware limits. Machines differ widely: some are laptops with integrated GPUs, while others are workstation-class servers with up to 128 GB of RAM and powerful GPUs. Consequently, the orchestrator adapts through hardware-aware scheduling.
Each environment selects one of three profiles: Laptop, Workstation; or Server, defined in a simple
resources.yamlfile:profile: workstation max_agent_runs: 4 gpu_memory_limit: 16000 cpu_cores: 8
During initialization, the active profile sets concurrency gates and resource budgets. Lightweight operations run together, while heavy tasks acquire locks before execution. A dual-lock system separates general resource tracking from expensive AI calls. This method maintains parallel work without conflict.
Scheduling moves through five stages: global concurrency check, CPU allocation, GPU budgeting, codex serialization, and cleanup. Each stage keeps the system predictable and stable. Cleanup routines always release resources, even after errors.
This approach brings precision and balance to orchestration rather than experimentation.
Despite these advantages, running a local-first AI orchestration platform introduces its own constraints. The system’s performance depends directly on available hardware, and smaller machines may need to rely on compact or quantized models such as Phi or Llama variants instead of large-scale cloud models. This balance between efficiency and accuracy requires careful model selection. In addition, while workstation-class setups with 128 GB of RAM can handle concurrent agents with ease, laptops or limited servers may experience slower inference or constrained multitasking. These realities remind developers that local-first design is not about matching the cloud’s abundance, but about achieving sustainable autonomy within real hardware boundaries.
Integrating the Model Context Protocol (MCP)
While a local platform values privacy, it still needs secure communication. The Model Context Protocol (MCP) provides structured interoperability for tools that observe or influence AI workflows.
The implementation, only 254 lines of code, supports two authentication modes: simple tokens for development and shared-secret tokens for production. It runs across HTTP, WebSocket, and TCP. As a result, the system remains flexible yet secure.
Through the MCP tool system, external services can register abilities such as
memory.readormemory.write. These allow dashboards, IDEs, or bots to stream workflow events in real time. For example, a Grafana panel can show resource usage, while an IDE plugin can display agent progress.In short, MCP turns a local orchestrator into a cooperative system—connected when needed, private by default.
For a deeper exploration of how MCP enables cross-agent collaboration, see Unlocking AI Collaboration with the Model Context Protocol.
A symbolic visual of the Model Context Protocol: where developer flow, memory, and modular context converge.
DAG-Based Workflow Execution
At its heart, orchestration is dependency management. The platform models workflows as directed acyclic graphs (DAGs), where each node represents a task and edges define dependencies.
A common configuration is:
plan → (backend, frontend) → (security, qa)
The product manager agent drafts a feature plan. Backend and frontend agents work in parallel. Security and QA agents then validate results. Prompts reuse earlier outputs through simple placeholders like
{backend.result}. The queue engine runs each step, stores results, and queues the next tasks until completion.This design preserves context, improves traceability, and supports recovery from partial failure. This emphasis on context-driven execution mirrors insights from AI Agents and Large Codebases: Why Context Beats Speed Every Time.
The Three-Tier Guardrail System
Stable orchestration requires discipline. Therefore, the platform applies a three-tier guardrail system.
- Input validation filters unsafe or malformed prompts.
- Runner control manages retries and captures runtime errors.
- Output checks reject empty or inconsistent responses.
All guardrail events are logged in
guardrail_metrics.jsonlwith categories such asguardrail_block,runner_error, andvalidator_block. Developers can view them directly:python -m agents.cli.main metrics guardrail --details 5
As a result, every failure becomes visible and fixable. Silent issues disappear.
The Eleven Expert Agents
Intelligence resides in the registry of eleven expert agents. They are grouped into development, security, and infrastructure domains.
- Development:
product_manager,bdd_backend,bdd_frontend,qa - Security:
security,validator,guardrail - Infrastructure:
database,networking,web3,encryption
Each agent includes a Pydantic schema defining its role and resource limits. During startup, these definitions convert to runtime specifications. This clear separation keeps the system flexible. Moreover, every action is logged, ensuring full transparency.
Built-In Web Dashboard
Transparency should not require the cloud. Instead, the platform provides a lightweight local web dashboard with seven views: system overview, workflows, guardrails, resources, agent timeline, MCP clients, and JSON API.
Each page loads in under 100 milliseconds and refreshes automatically. It remains responsive, simple, and always available—even offline.
Context Management and Memory
Persistent context keeps intelligence coherent. The SQLite-backed memory system uses two tables:
memoryfor key-value data andhistoryfor append-only logs.Agents use REST or MCP calls to read and write context. This lets long workflows maintain state between runs. As a result, agents can recall past outputs or user preferences without external storage.
Developer Experience and Automation
Starting up is simple:
python -m agents.cli.main init --profile laptop
This single command creates all configuration files, chooses a hardware profile, and prepares directories. The CLI also scaffolds projects in five languages: Python, Go, React, PHP, and Perl. Each uses templates with variable substitution for fast setup.
With more than twenty commands and six sub-apps, Typer provides clear and self-documented interfaces. Consequently, the CLI becomes both toolkit and guide.
A BDD-Driven Development Journey
Development followed seven BDD cycles, each improving a key feature:
- MCP authentication and security
- Zero-friction initialization
- API deduplication
- Resource scheduling
- Dashboard observability
- Advanced resource tracking
- Fail-fast initialization
Each cycle used RED-GREEN-REFACTOR testing and generated living Gherkin documentation. As a result, coverage now exceeds 85 percent, keeping behavior predictable while features evolve.
A visual metaphor of how structured thinking, like Gherkin and Behavior-Driven Development, helps AI systems connect human intent with machine execution.
The importance of clear behavioral documentation aligns closely with ideas from AI, Gherkin, and the Future of Software Development: Why Behavior-Driven Development Matters.Production Readiness and Lessons Learned
The final system demonstrates production-level quality. It includes thread-safe scheduling, clear error handling, and real-time monitoring. JSONL metrics make audits simple. Configuration is idempotent and safe to repeat.
Key technical innovations include:
- Fail-fast error handling with clear fixes
- Append-only metrics for transparency
- Dual-lock control for parallel work
- Hot-swappable agent settings
- Hardware-aware scaling across profiles
Building locally highlighted several truths. Simplicity brings reliability. In addition, insight into system behavior is essential. Developer experience shapes success as much as model accuracy. Above all, privacy and control can align with capability.
The platform now runs seamlessly across laptops, workstations, and servers. Each profile is tuned to its limits, and each agent knows its role.
The Future of Local-First AI Orchestration Platforms
The local-first AI orchestration platform proves that autonomy and performance can coexist. It respects hardware, protects data, and offers hybrid flexibility. In practice, it shows that orchestration can be as private as computation itself. This serves as a foundation for tools that return control to their builders.
Next comes refinement: wider support for edge devices, stronger context management, and closer integration with ecosystems such as Claude CLI and OpenAI APIs. Although the system is already production-grade, its deeper importance lies in the idea it represents: local-first intelligence as a craft, not a slogan.
The cloud will always have its place. However, it should never be the only place. Ultimately, true orchestration begins where control is personal.
The next frontier of AI engineering will not be written in the cloud alone. It will emerge from local workstations, developer labs, and edge devices where privacy and autonomy coexist. If this vision of local-first orchestration resonates with your work or research, share your thoughts, build upon the concept, or join the discussion on how to design systems that respect both hardware and humanity. Real progress begins when we question the defaults and start building differently.
What is a local-first AI orchestration platform?
A local-first AI orchestration platform manages multiple AI agents directly on local hardware instead of relying on cloud APIs. It improves privacy, reduces cost, and increases control over performance.
How does hardware-aware scheduling improve AI orchestration?
It adapts task execution to available resources such as CPU cores and GPU memory, ensuring stability on devices ranging from laptops to 128 GB workstations.
What role does the Model Context Protocol (MCP) play?
MCP enables secure communication between agents and external tools, allowing dashboards and IDEs to interact with workflows in real time while maintaining local control.
Can local-first systems replace cloud orchestration entirely?
Not completely. The cloud remains valuable for large-scale training and inference. Local-first orchestration complements it by offering autonomy, speed, and privacy for smaller or sensitive workflows.Key Takeaways
- A local-first AI orchestration platform enhances autonomy, privacy, and cost control by running AI agents directly on local hardware.
- It features a three-layer architecture: CLI for commands, Orchestrator for task management, and Registry for defining agent intelligence.
- The platform employs hardware-aware scheduling to optimize performance based on device capabilities, such as laptops or servers.
- The Model Context Protocol (MCP) facilitates secure communication between agents and external tools while maintaining local control.
- Its future includes support for edge devices and deeper integration with existing ecosystems, emphasizing personal control over AI workflows.
-
Building a Local-First Multi-Agent Orchestration Platform
The Problem with Cloud-Centric AI vs Local-First AI Orchestration
The cloud has long been the default stage for artificial intelligence. Frameworks such as LangChain, AutoGen, and CrewAI make it possible to orchestrate local or hosted models. However, their design still leans toward API-based, cloud-first execution. That approach works for experimentation, yet it introduces a clear weakness: dependence.
This return to autonomy echoes the early days of personal computing explored in Riding the Waves: From Home Computers to AI Orchestration, where individual control shaped innovation before the cloud era began.
From cassette tapes and floppy disks to orchestrated AI systems, computing has evolved through every wave.Every remote call carries both cost and exposure. Sensitive data must leave the machine to be processed elsewhere. Token-based billing discourages iteration. Even when using secure endpoints, developers trade autonomy for convenience. As a result, innovation is often limited by infrastructure.
A local-first approach changes that balance. It focuses on privacy, predictability, and cost control by running agents directly on local hardware. The cloud remains useful for large or complex tasks, yet local processing gives developers freedom. It does not reject connectivity; instead, it restores choice.
That principle guided the creation of a production-grade orchestration platform of roughly 3,700 lines of Python. Through seven BDD development cycles and a 96.5 percent test pass rate, it proved that a reliable system can run with zero external dependencies. Using SQLite and JSONL metrics, the same codebase coordinates multiple AI agents securely, predictably, and locally across devices.
Three-Layer Architecture of a Local-First AI Orchestration Platform
The system follows three clear layers: CLI, Orchestrator, and Registry. Each layer handles a specific function in the orchestration lifecycle.
The CLI layer, built with Typer, serves as the command surface. It offers more than twenty commands and about six hundred lines of code. Developers can initialize environments, run agents, and invoke workflows. This layer is the human-facing edge of the platform.
The Orchestrator layer, written with FastAPI, acts as the control center. It manages scheduling, routing, and task lifecycles. Its asynchronous design lets small tasks run in parallel while heavy inference jobs are handled one at a time. The main application file stays compact and easy to read.
The Registry layer defines intelligence. Eleven expert agents are declared in Pydantic configurations that describe capabilities, dependencies, and budgets. New agents can be added or updated with simple configuration changes.
FastAPI was chosen for its async speed and automatic schema generation. SQLite replaced Redis to stay aligned with the local-first approach. JSONL metrics were selected for their simplicity and transparency. As a result, commands call APIs, APIs invoke agents, and agents return results through a steady feedback loop.
These principles align with the broader ethical and security implications discussed in AI Orchestration, Security, and the Future of Work, where resilience and accountability shape the next phase of automation.
Hardware-Aware Resource Scheduling in a Local-First AI Orchestration Platform
Local-first systems must respect hardware limits. Machines differ widely: some are laptops with integrated GPUs, while others are workstation-class servers with up to 128 GB of RAM and powerful GPUs. Consequently, the orchestrator adapts through hardware-aware scheduling.
Each environment selects one of three profiles: Laptop, Workstation; or Server, defined in a simple
resources.yamlfile:profile: workstation max_agent_runs: 4 gpu_memory_limit: 16000 cpu_cores: 8
During initialization, the active profile sets concurrency gates and resource budgets. Lightweight operations run together, while heavy tasks acquire locks before execution. A dual-lock system separates general resource tracking from expensive AI calls. This method maintains parallel work without conflict.
Scheduling moves through five stages: global concurrency check, CPU allocation, GPU budgeting, codex serialization, and cleanup. Each stage keeps the system predictable and stable. Cleanup routines always release resources, even after errors.
This approach brings precision and balance to orchestration rather than experimentation.
Despite these advantages, running a local-first AI orchestration platform introduces its own constraints. The system’s performance depends directly on available hardware, and smaller machines may need to rely on compact or quantized models such as Phi or Llama variants instead of large-scale cloud models. This balance between efficiency and accuracy requires careful model selection. In addition, while workstation-class setups with 128 GB of RAM can handle concurrent agents with ease, laptops or limited servers may experience slower inference or constrained multitasking. These realities remind developers that local-first design is not about matching the cloud’s abundance, but about achieving sustainable autonomy within real hardware boundaries.
Integrating the Model Context Protocol (MCP)
While a local platform values privacy, it still needs secure communication. The Model Context Protocol (MCP) provides structured interoperability for tools that observe or influence AI workflows.
The implementation, only 254 lines of code, supports two authentication modes: simple tokens for development and shared-secret tokens for production. It runs across HTTP, WebSocket, and TCP. As a result, the system remains flexible yet secure.
Through the MCP tool system, external services can register abilities such as
memory.readormemory.write. These allow dashboards, IDEs, or bots to stream workflow events in real time. For example, a Grafana panel can show resource usage, while an IDE plugin can display agent progress.In short, MCP turns a local orchestrator into a cooperative system—connected when needed, private by default.
For a deeper exploration of how MCP enables cross-agent collaboration, see Unlocking AI Collaboration with the Model Context Protocol.
A symbolic visual of the Model Context Protocol: where developer flow, memory, and modular context converge.
DAG-Based Workflow Execution
At its heart, orchestration is dependency management. The platform models workflows as directed acyclic graphs (DAGs), where each node represents a task and edges define dependencies.
A common configuration is:
plan → (backend, frontend) → (security, qa)
The product manager agent drafts a feature plan. Backend and frontend agents work in parallel. Security and QA agents then validate results. Prompts reuse earlier outputs through simple placeholders like
{backend.result}. The queue engine runs each step, stores results, and queues the next tasks until completion.This design preserves context, improves traceability, and supports recovery from partial failure. This emphasis on context-driven execution mirrors insights from AI Agents and Large Codebases: Why Context Beats Speed Every Time.
The Three-Tier Guardrail System
Stable orchestration requires discipline. Therefore, the platform applies a three-tier guardrail system.
- Input validation filters unsafe or malformed prompts.
- Runner control manages retries and captures runtime errors.
- Output checks reject empty or inconsistent responses.
All guardrail events are logged in
guardrail_metrics.jsonlwith categories such asguardrail_block,runner_error, andvalidator_block. Developers can view them directly:python -m agents.cli.main metrics guardrail --details 5
As a result, every failure becomes visible and fixable. Silent issues disappear.
The Eleven Expert Agents
Intelligence resides in the registry of eleven expert agents. They are grouped into development, security, and infrastructure domains.
- Development:
product_manager,bdd_backend,bdd_frontend,qa - Security:
security,validator,guardrail - Infrastructure:
database,networking,web3,encryption
Each agent includes a Pydantic schema defining its role and resource limits. During startup, these definitions convert to runtime specifications. This clear separation keeps the system flexible. Moreover, every action is logged, ensuring full transparency.
Built-In Web Dashboard
Transparency should not require the cloud. Instead, the platform provides a lightweight local web dashboard with seven views: system overview, workflows, guardrails, resources, agent timeline, MCP clients, and JSON API.
Each page loads in under 100 milliseconds and refreshes automatically. It remains responsive, simple, and always available—even offline.
Context Management and Memory
Persistent context keeps intelligence coherent. The SQLite-backed memory system uses two tables:
memoryfor key-value data andhistoryfor append-only logs.Agents use REST or MCP calls to read and write context. This lets long workflows maintain state between runs. As a result, agents can recall past outputs or user preferences without external storage.
Developer Experience and Automation
Starting up is simple:
python -m agents.cli.main init --profile laptop
This single command creates all configuration files, chooses a hardware profile, and prepares directories. The CLI also scaffolds projects in five languages: Python, Go, React, PHP, and Perl. Each uses templates with variable substitution for fast setup.
With more than twenty commands and six sub-apps, Typer provides clear and self-documented interfaces. Consequently, the CLI becomes both toolkit and guide.
A BDD-Driven Development Journey
Development followed seven BDD cycles, each improving a key feature:
- MCP authentication and security
- Zero-friction initialization
- API deduplication
- Resource scheduling
- Dashboard observability
- Advanced resource tracking
- Fail-fast initialization
Each cycle used RED-GREEN-REFACTOR testing and generated living Gherkin documentation. As a result, coverage now exceeds 85 percent, keeping behavior predictable while features evolve.
A visual metaphor of how structured thinking, like Gherkin and Behavior-Driven Development, helps AI systems connect human intent with machine execution.
The importance of clear behavioral documentation aligns closely with ideas from AI, Gherkin, and the Future of Software Development: Why Behavior-Driven Development Matters.Production Readiness and Lessons Learned
The final system demonstrates production-level quality. It includes thread-safe scheduling, clear error handling, and real-time monitoring. JSONL metrics make audits simple. Configuration is idempotent and safe to repeat.
Key technical innovations include:
- Fail-fast error handling with clear fixes
- Append-only metrics for transparency
- Dual-lock control for parallel work
- Hot-swappable agent settings
- Hardware-aware scaling across profiles
Building locally highlighted several truths. Simplicity brings reliability. In addition, insight into system behavior is essential. Developer experience shapes success as much as model accuracy. Above all, privacy and control can align with capability.
The platform now runs seamlessly across laptops, workstations, and servers. Each profile is tuned to its limits, and each agent knows its role.
The Future of Local-First AI Orchestration Platforms
The local-first AI orchestration platform proves that autonomy and performance can coexist. It respects hardware, protects data, and offers hybrid flexibility. In practice, it shows that orchestration can be as private as computation itself. This serves as a foundation for tools that return control to their builders.
Next comes refinement: wider support for edge devices, stronger context management, and closer integration with ecosystems such as Claude CLI and OpenAI APIs. Although the system is already production-grade, its deeper importance lies in the idea it represents: local-first intelligence as a craft, not a slogan.
The cloud will always have its place. However, it should never be the only place. Ultimately, true orchestration begins where control is personal.
The next frontier of AI engineering will not be written in the cloud alone. It will emerge from local workstations, developer labs, and edge devices where privacy and autonomy coexist. If this vision of local-first orchestration resonates with your work or research, share your thoughts, build upon the concept, or join the discussion on how to design systems that respect both hardware and humanity. Real progress begins when we question the defaults and start building differently.
What is a local-first AI orchestration platform?
A local-first AI orchestration platform manages multiple AI agents directly on local hardware instead of relying on cloud APIs. It improves privacy, reduces cost, and increases control over performance.
How does hardware-aware scheduling improve AI orchestration?
It adapts task execution to available resources such as CPU cores and GPU memory, ensuring stability on devices ranging from laptops to 128 GB workstations.
What role does the Model Context Protocol (MCP) play?
MCP enables secure communication between agents and external tools, allowing dashboards and IDEs to interact with workflows in real time while maintaining local control.
Can local-first systems replace cloud orchestration entirely?
Not completely. The cloud remains valuable for large-scale training and inference. Local-first orchestration complements it by offering autonomy, speed, and privacy for smaller or sensitive workflows.Key Takeaways
- A local-first AI orchestration platform enhances autonomy, privacy, and cost control by running AI agents directly on local hardware.
- It features a three-layer architecture: CLI for commands, Orchestrator for task management, and Registry for defining agent intelligence.
- The platform employs hardware-aware scheduling to optimize performance based on device capabilities, such as laptops or servers.
- The Model Context Protocol (MCP) facilitates secure communication between agents and external tools while maintaining local control.
- Its future includes support for edge devices and deeper integration with existing ecosystems, emphasizing personal control over AI workflows.
-
MOBA Spellcasters Chronicles, which actually didn’t suck, is sunsetting June 19
🔗 https://massivelyop.com/2026/05/21/moba-spellcasters-chronicles-which-actually-didnt-suck-is-sunsetting-june-19
#SpellcastersChronicles #QuanticDream -
If you happen to be using exist.io, what do you think of this suggestion I made?
I essentially want to be able to treat a Category of Tags as data so that I can see it in trend graphs.
https://changemap.co/hellocode/exist/task/11151-treat-category-as-data-for/
-
🎮 Ho provato Spellcasters Chronicles, il nuovo MOBA di Quantic Dream: un viaggio emozionante nel mondo del gaming! #QuanticDream #SpellcastersChronicles
🔗 https://www.tomshw.it/videogioco/provato-spellcasters-chronicles-il-moba-di-quantic-dream
-
🎮 Ho provato Spellcasters Chronicles, il nuovo MOBA di Quantic Dream: un viaggio emozionante nel mondo del gaming! #QuanticDream #SpellcastersChronicles
🔗 https://www.tomshw.it/videogioco/provato-spellcasters-chronicles-il-moba-di-quantic-dream
-
يبدو أن ممثل Detroit: Become Human يلمح لشيء ما قادم في حلقة State of Play VGA4A - اخبار العاب الفيديو
أعاد إعلان سوني عن موعد عرض حلقة State of Play المرتقب في 12 فبراير الأنظار إلى لعبة Detroit: Become Human، بعدما تفاعل براين ديكارت، مؤدي شخصية “كونور”، مع الخبر بإشارة مقتضبة لكنها كافية لإشعال التكهنات داخل مجتمع بلايستيشن. سوني كانت قد أكدت رسميًا، أن بث حلقة State of Play القادم سيُقام في بعد 12 فبراير … #Games #ألعاب #PS5Pro # #Playstation #PlayStationStateOfPlay #QuanticDream -
يبدو أن ممثل Detroit: Become Human يلمح لشيء ما قادم في حلقة State of Play VGA4A - اخبار العاب الفيديو
أعاد إعلان سوني عن موعد عرض حلقة State of Play المرتقب في 12 فبراير الأنظار إلى لعبة Detroit: Become Human، بعدما تفاعل براين ديكارت، مؤدي شخصية “كونور”، مع الخبر بإشارة مقتضبة لكنها كافية لإشعال التكهنات داخل مجتمع بلايستيشن. سوني كانت قد أكدت رسميًا، أن بث حلقة State of Play القادم سيُقام في بعد 12 فبراير … #Games #ألعاب #PS5Pro # #Playstation #PlayStationStateOfPlay #QuanticDream -
Is there any open source software that can display my calendars, träwelling data and gadgetbridge data in one view?
-
Is there any open source software that can display my calendars, träwelling data and gadgetbridge data in one view?
-
Is there any open source software that can display my calendars, träwelling data and gadgetbridge data in one view?
-
Erstes Fazit zur Nacht: 😴
Das Schlaftracking lag direkt daneben – Einschlafen laut Pixel erst um 02:00, real (und laut Apple Watch) war es 22:00 Uhr. 📉
Spannend: Ich konnte die Zeit in der Fitbit-App manuell korrigieren (Danke AWU für den Spickzettel 📝). Daraufhin hat Fitbit tatsächlich alle Schlafphasen nachträglich korrekt berechnet. Die Daten waren also da, nur die Erkennung hat gepennt. Ich beobachte weiter! 👀
-
🕹️ Immergiti nel mondo di Quantic Dream! Prova gratis il loro emozionante nuovo titolo multiplayer. Non perdere l'opportunità! #GamingGratis #QuanticDream
-
🎮 Sperimentate l'adrenalina del nuovo titolo multiplayer di Quantic Dream! Provalo gratis NOW! #GamingGratis #QuanticDream
-
خصم Detroit: Become Human يدفع اللعبة إلى قمة نشاطها على Steam VGA4A - اخبار العاب الفيديو
رغم إصدار لعبة Detroit: Become Human منذ 8 سنوات تقريبًا، فقد عادت اللعبة لتتصدر المشهد من جديد على منصة Steam، محققة واحدة من أقوى مفاجآت سوق الألعاب مع نهاية 2025 وبداية 2026 بسبب الخصم الرهيب التي حصلت عليه خلال الأيام الماضية. نجحت Detroit: Become Human في بيع ما يقارب مليون نسخة خلال أسبوعين فقط، لتصبح … #Games #ألعاب # #DetroitBecomeHuman #QuanticDream https://www.vga4a.com/archives/301933 -
CW: Body weight
Last year, I tried out calorie counting and macronutrient estimation in ”hard mode” for a while. I used Chronometer and SnapCalorie, went through the trouble of weighing individual recipe items when cooking myself, and entering data from nutrition labels. My main intent was to shed light to the macronutrient side of things, especially protein (I’m vegetarian and an occasional fish-eater).
Calorie counting itself started to noticeably reduce my energy input - I just couldn’t be arsed to eat that chocolate because I’d have to enter the data into the app.
Both SnapCalorie and Chronometer have a way to estimate macros and energy from a photo. Comparing their results against a dish I made and measured from scratch, it’s in the ballpark. But if one would be aiming at a modest, say, 100 kcal/d reduction in intake, the error margin is far too great to rely on photo based estimation.
Being satisfied with the macronutrient data, I got interested in the energy side of things. I dug up a bunch of body weight models - the 1958 linear model, the Kevin Hall / NIH model from 2011, and the Pennington / Diana Hall model, introduced around the same time.
My weekly weighing is usually stable, within +/-0.5 kg. Just for science, I put myself on a huge energy deficit of 688 kcal/d (weekly average, ex post facto, against realtime expenditure from Garmin) and tracked my weight and body composition with InBody scans.
After this miserable intervention, about 1/3 of weight loss was muscle, and otherwise the weight loss tracked the NIH model exactly. With a sample size of one, at least for short term, that model is the clear winner. It took me much longer to get the lost muscle mass back. Can’t recommend. #QuantifiedSelf #weightloss
-
Alors que Quantic Dream et son David Cage essaient de détourner l'attention, l'information importante à retenir sur l'actualité du studio, c'est que la Cour de cassation a cassé le jugement de la Cour d'appel concernant son jugement contre son ancien employé, chef du service informatique. La Cour reconnaît que son ancien chef du service informatique « a bien droit à des dommages et intérêts, mais aussi que la prise d’acte de rupture devra être reconnue. L’affaire devra repasser une dernière fois devant la cour d’appel – sans doute pas avant un an – pour que la procédure soit enfin close. »
-
Alors que Quantic Dream et son David Cage essaient de détourner l'attention, l'information importante à retenir sur l'actualité du studio, c'est que la Cour de cassation a cassé le jugement de la Cour d'appel concernant son jugement contre son ancien employé, chef du service informatique. La Cour reconnaît que son ancien chef du service informatique « a bien droit à des dommages et intérêts, mais aussi que la prise d’acte de rupture devra être reconnue. L’affaire devra repasser une dernière fois devant la cour d’appel – sans doute pas avant un an – pour que la procédure soit enfin close. »
-
Alors que Quantic Dream et son David Cage essaient de détourner l'attention, l'information importante à retenir sur l'actualité du studio, c'est que la Cour de cassation a cassé le jugement de la Cour d'appel concernant son jugement contre son ancien employé, chef du service informatique. La Cour reconnaît que son ancien chef du service informatique « a bien droit à des dommages et intérêts, mais aussi que la prise d’acte de rupture devra être reconnue. L’affaire devra repasser une dernière fois devant la cour d’appel – sans doute pas avant un an – pour que la procédure soit enfin close. »
-
Alors que Quantic Dream et son David Cage essaient de détourner l'attention, l'information importante à retenir sur l'actualité du studio, c'est que la Cour de cassation a cassé le jugement de la Cour d'appel concernant son jugement contre son ancien employé, chef du service informatique. La Cour reconnaît que son ancien chef du service informatique « a bien droit à des dommages et intérêts, mais aussi que la prise d’acte de rupture devra être reconnue. L’affaire devra repasser une dernière fois devant la cour d’appel – sans doute pas avant un an – pour que la procédure soit enfin close. »
-
Spellcasters Chronicles Announced as 3v3 Action Strategy Game
https://fullcleared.com/news/spellcasters-chronicles-announced-as-3v3-action-strategy-game/
#gaming #gamingnews #videogames #spellcasterschronicles #quanticdream
-
newsletter #QuanticDream
se dividen en dos equipos y desarrollan dos juegos en paralelo -
newsletter #QuanticDream
se dividen en dos equipos y desarrollan dos juegos en paralelo -
newsletter #QuanticDream
se dividen en dos equipos y desarrollan dos juegos en paralelo -
newsletter #QuanticDream
se dividen en dos equipos y desarrollan dos juegos en paralelo -
🎮 Quantic Dream porta la magia del multiplayer a Spellcasters Chronicles! Preparatevi per una nuova, avvincente avventura! #SpellcastersChronicles #QuanticDreamMultiplayer
🔗 https://www.tomshw.it/videogioco/spellcasters-chronicles-quantic-dream-diventa-multiplayer-anteprima
-
🔮 Immergiti nel mondo di Spellcasters Chronicles, la nuova avventura multiplayer di Quantic Dream! Un'avventura sorprendente da non perdere. #MultiplayerMagic #QuanticDream
-
🧐 Ah, the deep musings of a quantum-savvy blogger, where solving hard problems is casually dismissed, and K-12 education gets a comedic nod. It's a riveting tale of hypothetical horrors, punctuated by the promise of a non-existent quantum savior 😆🔮. Meanwhile, Zvi Mowshowitz is hailed as the messiah of educational reform 👨🏫✨.
https://scottaaronson.blog/?p=9082 #quantumeducation #comedicblogging #ZviMowshowitz #problem-solving #educationalreform #hypotheticalhorrors #HackerNews #ngated