# Writing

Source: https://satunix.github.io/site/beta/blog/

- [Why more agent autonomy creates a security architecture problem](https://satunix.github.io/site/beta/blog/agent-autonomy-is-a-security-architecture-problem.md) (2026-09-23, draft): Authority, delegation, trust boundaries and least privilege, once the thing acting on your behalf makes its own decisions.
- [Why agent memory is not just a vector database](https://satunix.github.io/site/beta/blog/agent-memory-is-not-a-vector-database.md) (2026-09-23, draft): Task state, provenance, authority and time all matter. Similarity search alone captures none of them.
- [Agents need a control plane, not just a system prompt](https://satunix.github.io/site/beta/blog/agents-need-a-control-plane.md) (2026-09-23, draft): A system prompt is a request, not a boundary. Tool-using agents need enforcement that sits outside the model.
- [Pentesting cloud IAM as a graph problem](https://satunix.github.io/site/beta/blog/cloud-iam-as-a-graph-problem.md) (2026-09-23, draft): Roles, trust policies, STS and cross-account access form a graph. Testing it means finding paths, not misconfigurations.
- [Designing cyber agents that know their rules of engagement](https://satunix.github.io/site/beta/blog/cyber-agents-and-rules-of-engagement.md) (2026-09-23, draft): Scope should be enforceable machine state, not prose buried in a prompt.
- [Dynamic delegation: letting agent topology follow the problem](https://satunix.github.io/site/beta/blog/dynamic-delegation.md) (2026-09-23, draft): Fixed multi-agent org charts may be the wrong abstraction. What if structure formed around each task instead?
- [Building an evidence-first AI pentesting agent](https://satunix.github.io/site/beta/blog/evidence-first-pentest-agents.md) (2026-09-23, draft): Findings, tool calls and conclusions should all resolve back to evidence. A design for AI-assisted testing that keeps humans in charge.
- [From pentester to adversarial systems engineer](https://satunix.github.io/site/beta/blog/from-pentester-to-adversarial-systems-engineer.md) (2026-09-23, draft): Offensive security increasingly runs through cloud, identity, APIs, CI/CD and autonomous systems. The job is changing shape.
- [Local AI as security infrastructure](https://satunix.github.io/site/beta/blog/local-ai-as-security-infrastructure.md) (2026-09-23, draft): Privacy, model control, isolation and reproducibility: why running models yourself matters beyond cost.
- [Building offensive infrastructure as infrastructure](https://satunix.github.io/site/beta/blog/offensive-infrastructure-as-infrastructure.md) (2026-09-23, draft): C2, telemetry, test environments and deployment pipelines deserve the same engineering discipline as production systems.
- [Recursive agents and the context problem](https://satunix.github.io/site/beta/blog/recursive-agents-and-the-context-problem.md) (2026-09-23, draft): How does a subagent know what it needs without inheriting the entire parent context?
- [Running 27B models on constrained hardware](https://satunix.github.io/site/beta/blog/running-27b-models-on-constrained-hardware.md) (2026-09-23, draft): Quantisation, the VRAM/RAM split, context size and throughput: lessons from running mid-size models on hardware that is not built for it.
- [The approval came after the action](https://satunix.github.io/site/beta/blog/the-approval-came-after-the-action.md) (2026-09-23, draft): An agent changed a file before the approval prompt said it was allowed to. Why UI-level approvals are not enforcement.
- [TTFT is often more important than tokens per second](https://satunix.github.io/site/beta/blog/ttft-matters-more-than-tokens-per-second.md) (2026-09-23, draft): For interactive and agent workloads, waiting for the first token shapes the experience more than raw generation speed.
- [What adversary emulation is actually for](https://satunix.github.io/site/beta/blog/what-adversary-emulation-is-for.md) (2026-09-23, draft): Not a trophy hunt. Attack-path discovery, telemetry, visibility gaps and proving that detections and playbooks work.
