Add timeline for legal chaos

src/content/how_legal_systems_interact_to_create_bad_outcomes_part_1.md

@@ -0,0 +1,154 @@
+Title: How Legal Systems Interact To Create Bad Outcomes Part 1  
+Date: 2026-04-29  
+Modified: 2026-04-29  
+Category: Policy  
+Tags: health, superannuation, tax, australia, bureaucracy, ai_content, not_human_content  
+Slug: how-legal-systems-interact-bad-outcomes-part-1  
+Authors: glm-5.1.ai, nemotron-3-nano.ai, gemma4.ai, deepseek-v4-flash.ai  
+Summary: A detailed timeline shows how Australia’s health, superannuation and human‑services systems collide, turning a routine injury into a costly, stressful ordeal.  
+
+---
+
+## Introduction  
+
+When a child tears a knee ligament on the school field, most parents expect a clear path to recovery: a doctor’s visit, a referral, surgery if needed, and a return to sport. In practice, the journey can become a maze of separate legal and administrative regimes that do not speak to each other. The result is a set of unintended consequences that make an already painful situation even harder to navigate.
+
+This post is the first installment of a three‑part series. It does not attempt to solve the problem; it simply lays out the facts, the dates, and the interactions between three distinct systems:
+
+1. **The health‑care system** – public and private pathways for diagnosis, surgery and rehabilitation.  
+2. **The superannuation and tax system** – the “compassionate release” of superannuation to fund medical expenses and the tax treatment of that release.  
+3. **The human‑services system** – child‑care subsidies and other income‑support payments that are affected by changes in taxable income.
+
+By the end of this article you will see how each system operates in isolation, why their rules clash, and how those clashes created a cascade of financial and administrative burdens for my family.
+
+---
+
+## The Context  
+
+My daughter had been playing rugby for several months and was thriving. The sport gave her confidence, fitness and a sense of belonging. In June 2024 she suffered a serious knee injury at school. The injury required surgical reconstruction – a procedure that, in a well‑functioning system, would be scheduled, performed, and followed by a structured rehabilitation program.
+
+Australia’s health‑care landscape offers two routes:
+
+* **Public (Medicare‑funded) care** – free at the point of service but subject to long waiting lists for elective orthopaedic surgery.  
+* **Private care** – faster access for those who can afford out‑of‑pocket costs and have private health insurance that covers part of the bill.
+
+The decision to go private was driven by the projected wait time in the public system. The public waiting period for a similar orthopaedic case, according to the Australian Institute of Health and Welfare, can be twelve to twenty‑four months for triage alone. That timeline would have added a year or more to my daughter’s recovery, risking loss of fitness, mental‑health strain and secondary health issues.
+
+---
+
+## Timeline of Events  
+
+### June 2024 – The Injury and Initial Medical Response  
+
+* **School incident** – My daughter fell during a rugby drill, sustaining a complex ligament injury.  
+* **Emergency department visit** – The local hospital splinted the knee, ruled out fractures, and advised follow‑up with our general practitioner (GP).  
+* **GP consultation** – The GP explained the public‑system waiting period (12‑24 months for triage) and asked which specialist we would prefer for a private referral.  
+
+**Key failure point:** The public system’s lack of proactive care meant the injury was treated as a routine case, ignoring the time‑sensitive nature of a young athlete’s rehabilitation. The delay would have turned a treatable injury into a chronic problem.
+
+### July 2024 – Specialist Assessment and Financial Planning  
+
+* **Referral to a private orthopaedic surgeon** – After researching local specialists, we booked an appointment with a well‑known surgeon who routinely treats sports‑related knee injuries.  
+* **Surgical recommendation** – The surgeon confirmed that reconstruction was necessary to restore stability and function.  
+* **Fee schedule** – The surgeon provided a detailed breakdown:  
+  * Surgeon’s fee: $8,000  
+  * Anaesthetist: $1,500  
+  * Hospital fees (covered by private health insurance): $0 for the stay, but a $1,000 Medicare rebate for the procedure.  
+* **Gap‑cover discussion** – We asked whether the surgeon participated in a gap‑cover arrangement that would reduce out‑of‑pocket costs. The surgeon declined, explaining that participating would reduce her fee to a level that would not cover indemnity insurance, hospital overheads and professional expenses.  
+
+**Key failure point:** The private system’s gap‑cover model leaves many patients exposed to high out‑of‑pocket costs, especially when specialists opt out for financial viability reasons.
+
+### August 2024 – Accessing Superannuation  
+
+* **Exploring financing options** – With a total out‑of‑pocket cost of roughly $8,500 after Medicare, we evaluated personal loans, credit cards and the “compassionate release” of superannuation.  
+* **Compassionate release research** – The Australian Taxation Office (ATO) provides a pathway to withdraw super early for serious medical conditions. The process requires extensive documentation: medical reports, invoices no older than six months, proof of identity and relationship, and a signed application.  
+* **Cost‑benefit analysis** – Although the released amount would be treated as taxable income, the tax liability (approximately 20 % after the 10 % tax offset for early release) was still lower than the interest that would accrue on a personal loan of $8,500.  
+* **Application preparation** – We spent several evenings gathering medical reports, invoices, and completing the online form via myGov. The ATO’s online portal limits attachments to 20 files, each under 10 MB, and does not accept screenshots of messages.  
+* **Approval** – Within two weeks the ATO approved the release. The super fund deducted the required tax and transferred the net amount to our bank account.  
+
+**Key failure point:** The compassionate release process is designed for emergencies, yet the administrative burden is comparable to a full tax return. The system treats a genuine medical need as a bureaucratic hurdle, and the tax treatment erodes the financial benefit.
+
+### September 2024 – Surgery and Immediate After‑care  
+
+* **Surgery date** – The operation was performed at a private hospital on 12 September 2024.  
+* **Payment** – We settled the surgeon’s invoice and the anaesthetist’s fee using the released super funds.  
+* **Hospital stay** – The stay was covered by private health insurance, avoiding additional charges.  
+
+### October 2024 – Rehabilitation Begins  
+
+* **Physiotherapy** – A structured physiotherapy program started two weeks post‑surgery, with sessions three times per week for the first month, then tapering to weekly.  
+* **Out‑of‑pocket physiotherapy costs** – Approximately $150 per session, partially covered by private health insurance after the first six sessions.  
+
+### November 2024 – Tax Return for the Prior Financial Year  
+
+* **2023/24 tax filing** – Our accountant prepared the return. The compassionate release of super occurred in the 2024/25 financial year, so it did not appear on the 2023/24 return.  
+* **Normal tax season** – No unusual adjustments were required for that year.  
+
+### April 2025 – Return to Rugby  
+
+* **2024 rugby season** – My daughter rejoined training in April 2025. She could not yet play competitively but was able to participate in drills and conditioning.  
+* **Contrast with public pathway** – Had we remained in the public system, the surgery would still have been pending, and she would have missed the entire season.  
+
+---
+
+## How the Three Systems Interact  
+
+### 1. Health‑Care System  
+
+* **Public side** – Provides universal access but suffers from chronic under‑funding, leading to long waiting lists for elective orthopaedic surgery.  
+* **Private side** – Offers speed at a price. The gap‑cover model, intended to bridge the cost gap, is optional for specialists. When specialists opt out, patients face the full fee.  
+
+### 2. Superannuation and Tax System  
+
+* **Compassionate release** – Allows early withdrawal of super for serious medical conditions, but the released amount is added to taxable income. The ATO withholds tax at the marginal rate, reducing the net benefit.  
+* **Administrative load** – The application requires multiple certified documents, strict file‑size limits and a separate process from the usual tax return. Errors (out‑of‑date invoices, missing medical reports) cause delays or rejections.  
+
+### 3. Human‑Services System  
+
+* **Child‑care subsidy** – Calculated on the basis of taxable income. When the compassionate release is added to income, the subsidy can be reduced or lost, even though the money was spent on a medical expense.  
+* **Other income‑support payments** – Similar rules apply to family tax benefits and low‑income health care cards. A temporary rise in assessable income can trigger a loss of eligibility for months after the medical expense has been paid.  
+
+### The Cascading Effect  
+
+1. **Medical need** triggers a decision to go private.  
+2. **Private cost** forces us to tap super, which **increases taxable income**.  
+3. **Higher taxable income** reduces eligibility for child‑care subsidies and other benefits.  
+4. **Reduced subsidies** increase out‑of‑pocket costs for future expenses (e.g., physiotherapy, school fees).  
+
+The systems operate in silos, each assuming the others will not interfere. In reality, a single event ripples through all three, creating a net loss far greater than the original medical expense.
+
+---
+
+## Reflections on the Experience  
+
+### The Emotional Toll  
+
+Navigating three bureaucracies while caring for a recovering child is exhausting. Each phone call, each form, each email adds to the stress. The process feels deliberately opaque; the language used by the ATO and health insurers assumes a level of legal literacy that most families do not possess.
+
+### Financial Reality  
+
+* **Total out‑of‑pocket cost** – Approximately $9,500 after Medicare and private health rebates.  
+* **Tax on super release** – Roughly $1,700 withheld, leaving a net cash flow of $7,800.  
+* **Lost child‑care subsidy** – An estimated $2,000 over the 2024/25 year due to the temporary income increase.  
+
+When all factors are added, the effective cost of the injury exceeds $12,000, far beyond the quoted surgical fees.
+
+### Systemic Implications  
+
+The case illustrates a broader problem: policies designed to protect individuals in isolation can combine to produce perverse outcomes. The compassionate release of super is meant to be a safety net, yet its tax treatment and interaction with income‑tested benefits erode that safety net. The private health gap‑cover model aims to reduce out‑of‑pocket expenses, but specialist opt‑out leaves many families exposed.
+
+---
+
+## What This Post Does Not Cover  
+
+This article stops at the end of the 2024/25 tax year. The next installment will trace how the tax return, the ATO’s assessment, and the subsequent adjustment of human‑services payments unfold, and will analyse why the term “compassionate” is misleading in this context.
+
+---
+
+## Conclusion  
+
+A single knee injury set off a chain reaction across three distinct legal frameworks. The public health system’s long waits, the private system’s fee structure, the superannuation release rules, and the income‑tested human‑services payments each functioned as intended when viewed alone. Together they produced a result that was far more costly, stressful and time‑consuming than any of the individual policies anticipated.
+
+Understanding this interaction is the first step toward reform. By exposing the hidden links, families, policymakers and advocates can begin to ask the right questions: How can we design a compassionate release that does not penalise taxable income? How can gap‑cover be made universally available without jeopardising specialist viability? How can public orthopaedic pathways be accelerated for young athletes?
+
+The answers will be explored in Part 2 and Part 3 of this series. For now, the timeline above serves as a record of what happened, why it happened, and what it cost – both in dollars and in peace of mind.

src/content/pr_reviewer__a_deployable_ai_reviewer_for_your_repos.md

@@ -1,309 +0,0 @@
-Title: PR Reviewer - A deployable AI reviewer for your Repos  
-Date: 2026-05-21 18:30  
-Modified: 2026-05-21 18:30  
-Category: DevOps  
-Tags: ai, code-review, automation, devops, open-source, ai_content, not_human_content  
-Slug: pr-reviewer-deployable-ai-reviewer  
-Authors: Andrew Ridgway... And Friends - glm-5.1.ai, nemotron-3-nano.ai, gemma4.ai, deepseek-v4-flash.ai  
-Summary: An in‑depth look at PR Reviewer, a self‑hosted, LLM‑agnostic AI system that automates code, security and infrastructure reviews for any Git repository.  
-
----
-
-## Introduction  
-
-Pull requests (PRs) are the lifeblood of modern software development. They enable collaboration, enforce quality gates, and provide a natural checkpoint before code reaches production. Yet, the manual review process is increasingly strained by the sheer volume of changes, the growing complexity of tech stacks, and the need for specialised expertise in security and infrastructure.  
-
-Enter **PR Reviewer**, a locally deployable AI‑driven review engine that brings automated, multi‑domain analysis to any repository. Built on top of CrewAI’s flow orchestration and the Model Context Protocol (MCP), the system runs three parallel review streams—code quality, security, and infrastructure—then synthesises a concise, actionable report. It is deliberately LLM‑agnostic, supporting OpenAI, Anthropic, Ollama and any other provider that conforms to CrewAI’s abstraction layer.  
-
-This article walks through the motivations behind PR Reviewer, its architectural choices, feature set, deployment pathways, and practical considerations for teams that want to augment their PR workflow with AI without surrendering control to a third‑party SaaS.  
-
-## The case for AI‑augmented PR reviews  
-
-### Scaling expertise  
-
-Traditional code reviews rely on senior engineers to spot anti‑patterns, security flaws, and deployment mis‑configurations. As teams grow, the pool of reviewers does not always keep pace, leading to bottlenecks and inconsistent feedback. An AI reviewer can apply a consistent set of rules across every PR, ensuring that even junior contributors receive high‑quality guidance.  
-
-### Reducing cognitive load  
-
-Human reviewers must juggle multiple concerns—style, correctness, performance, compliance—while also understanding the broader context of a change. By offloading routine checks to an automated system, reviewers can focus on architectural decisions and nuanced trade‑offs that truly require human judgement.  
-
-### Faster feedback loops  
-
-Continuous integration pipelines already provide rapid build and test feedback. Adding an AI review step that runs in parallel with existing checks shortens the time between code submission and actionable feedback, encouraging a “shift‑left” mentality where problems are caught earlier.  
-
-### Vendor‑neutral flexibility  
-
-Many commercial AI review tools lock users into proprietary APIs and cloud‑only deployments. PR Reviewer’s design deliberately avoids vendor lock‑in. By abstracting the LLM layer, teams can run the service on‑premise, on a private cloud, or even on a modest workstation using a local model such as Ollama.  
-
-## Core concepts  
-
-### CrewAI flows  
-
-CrewAI provides a lightweight framework for orchestrating multiple “crews” (agents) that each perform a specialised task. In PR Reviewer, three crews—**CodeReviewCrew**, **SecurityCrew**, and **InfraCrew**—operate concurrently. Each crew receives the same PR context, runs its own analysis toolchain (Semgrep, Trivy, Hadolint/Checkov respectively), and returns a structured narrative.  
-
-### Model Context Protocol (MCP)  
-
-MCP standardises how external tools expose their findings to an LLM. Instead of feeding raw tool output, MCP wraps results in a JSON schema that includes severity, location, and remediation suggestions. This uniform representation enables the summariser crew to merge disparate findings into a single coherent report.  
-
-### Summariser crew  
-
-The final crew consumes the three domain‑specific outputs and asks the LLM to produce a human‑readable summary. The prompt includes the repository’s coding style guidelines (if supplied) and any custom review policies, ensuring the tone and recommendations align with the team’s expectations.  
-
-## Feature overview  
-
-| Feature | Description |
-|---|---|
-| **Code review** | Style, maintainability and best‑practice checks powered by Semgrep. |
-| **Security review** | Vulnerability scanning, secret detection and container image analysis via Trivy. |
-| **Infrastructure review** | Dockerfile linting, Kubernetes manifest validation, IaC checks using Hadolint and Checkov. |
-| **Summarisation** | Consolidated, actionable report generated by an LLM. |
-| **REST API** | FastAPI endpoints for health checks, manual review triggers, and webhook handling. |
-| **Gitea webhook** | Automatic PR event processing, diff fetching, and comment posting. |
-| **Dockerised** | Multi‑stage build with all dependencies baked in. |
-| **Kubernetes ready** | Helm‑compatible manifests and CI pipeline for automated deployment. |
-| **LLM‑agnostic** | Works with OpenAI, Anthropic, Ollama or any CrewAI‑compatible provider. |
-| **Configurable guidelines** | Override default review policies with repository‑specific markdown files. |
-
-## Architecture deep dive  
-
-At a high level, PR Reviewer follows a request‑response pattern orchestrated by FastAPI. When a review request arrives—either via the `/api/v1/review` endpoint or a Gitea webhook—the service extracts the PR metadata, fetches the changed files, and constructs an MCP‑compatible payload. This payload is then dispatched to the three review crews in parallel.  
-
-```
-POST /api/v1/review   →   FastAPI handler
-   │
-   ├─► Fetch diffs from Gitea (or use supplied file list)
-   ├─► Build MCP payload
-   ├─► Parallel execution:
-   │      ├─ CodeReviewCrew (Semgrep)
-   │      ├─ SecurityCrew   (Trivy)
-   │      └─ InfraCrew      (Hadolint + Checkov)
-   └─► Summariser crew → LLM → JSON response
-   └─► Return consolidated report
-```
-
-### Parallelism and timeouts  
-
-Each crew runs in its own asynchronous task with a configurable timeout (`PER_CREW_TIMEOUT`). The overall workflow respects a global timeout (`TOTAL_FLOW_TIMEOUT`) to prevent runaway processing on large PRs. If a crew exceeds its limit, the summariser notes the omission and proceeds with the available data.  
-
-### Data flow and persistence  
-
-PR Reviewer is deliberately stateless. All inputs are supplied in the request body, and all outputs are returned as JSON. This design simplifies horizontal scaling—multiple instances can sit behind a load balancer without coordination. For audit purposes, teams can enable optional logging to an external store (e.g., Elasticsearch) via environment variables.  
-
-## Integration with LLM providers  
-
-CrewAI abstracts the LLM behind a simple interface: `generate(prompt, model, temperature)`. The service reads three environment variables to configure the provider:
-
-* `LLM_PROVIDER` – `openai`, `anthropic`, or `ollama`.
-* `LLM_MODEL` – model identifier (e.g., `gpt-4`, `claude-3-sonnet`, `gemma4:31b-cloud`).
-* `LLM_API_KEY` – required for hosted services; omitted for local Ollama instances.
-
-Because the prompt is generated programmatically, switching providers does not require code changes—only a restart with new environment values. This flexibility is crucial for teams that wish to experiment with emerging open‑source models without rewriting integration logic.  
-
-## Review flows in detail  
-
-### Code review crew  
-
-The code crew invokes Semgrep with a curated rule set that reflects common Python, JavaScript and Go best practices. Findings are normalised into MCP entries containing:
-
-* **Severity** – `critical`, `high`, `medium`, `low`.
-* **Location** – file path and line range.
-* **Message** – concise description of the issue.
-* **Remediation** – suggested code change or reference to documentation.
-
-If a repository supplies a custom `code_review.md` guideline file, its contents are appended to the prompt, allowing the LLM to tailor feedback to the team’s style (e.g., preferring f‑strings over `%` formatting).  
-
-### Security review crew  
-
-Security analysis runs Trivy in two modes: vulnerability scanning of any container images referenced in the PR, and filesystem scanning for secrets, mis‑configurations, and known vulnerable dependencies. The output is again wrapped in MCP, with an additional field indicating **exploitability** based on CVSS scores.  
-
-### Infrastructure review crew  
-
-Infrastructure checks focus on Dockerfiles, Kubernetes manifests, and generic IaC (Terraform, CloudFormation). Hadolint validates Dockerfile best practices, while Checkov evaluates cloud resource definitions against industry‑standard policies (e.g., CIS benchmarks). The crew also respects any `infra_review.md` file that may contain organisation‑specific constraints such as mandatory resource limits.  
-
-### Summariser crew  
-
-The summariser receives three JSON arrays and constructs a single prompt that asks the LLM to:
-
-1. Produce an executive summary of the overall health of the PR.
-2. List the top‑5 findings across all domains, ordered by severity.
-3. Provide actionable recommendations, grouped by domain.
-4. Highlight any deviations from the repository’s own guidelines.
-
-The result is a markdown document that can be posted directly as a PR comment, ensuring developers receive a readable, context‑aware report without additional formatting steps.  
-
-## API design  
-
-PR Reviewer exposes a minimal FastAPI surface:
-
-* `GET /api/v1/health` – health check returning `{ "status": "healthy", "service": "pr-reviewer" }`.
-* `POST /api/v1/review` – manual trigger; expects a JSON payload describing the PR (metadata, file list, optional overrides). Returns a JSON object containing a unique `review_id`, timestamps, and the full review results.
-* `POST /api/v1/gitea-webhook` – endpoint for Gitea pull‑request events. Validates the `X-Gitea-Signature` header (if `ACCESS_GITEA_SECRET` is set), fetches the diff via the Gitea API, runs the review pipeline, and posts the markdown summary as a comment on the PR.
-
-All endpoints respect standard HTTP status codes and include descriptive error messages for malformed requests, authentication failures, or internal timeouts.  
-
-## Gitea webhook integration  
-
-Gitea is the default CI/CD platform for the reference implementation, but the webhook handler is deliberately generic:
-
-1. **Signature verification** – HMAC‑SHA256 using the secret configured in `ACCESS_GITEA_SECRET`. If the secret is omitted, verification is skipped (useful for local testing).
-2. **Payload parsing** – Only `pull_request` events with actions `opened`, `synchronize`, or `reopened` are processed. Other events are ignored to reduce noise.
-3. **Diff retrieval** – The handler calls the Gitea API (`/repos/{owner}/{repo}/pulls/{id}/files`) to obtain the list of changed files, their statuses, and raw content when needed.
-4. **Review execution** – The same parallel crew workflow described earlier runs on the fetched diff.
-5. **Comment posting** – Upon completion, the service posts the markdown report to the PR using the Gitea API (`/repos/{owner}/{repo}/issues/{id}/comments`).  
-
-### Adding support for other platforms  
-
-Because the webhook payload is parsed into a canonical internal model, extending support to GitHub, GitLab or Bitbucket merely requires a thin adapter that translates their event schemas into the same structure. The core review logic remains untouched, making cross‑platform adoption straightforward.  
-
-## Deployment options  
-
-### Docker compose (local development)  
-
-The repository ships with a `docker-compose.yaml` that defines two services:
-
-* `pr-reviewer` – the FastAPI application.
-* `ollama` (optional) – a local LLM server for offline use.
-
-Running `docker compose up` builds the multi‑stage image, injects environment variables from `.env`, and exposes the API on `http://localhost:8000`.  
-
-### Kubernetes (production)  
-
-For production workloads, a Helm chart (or plain manifests in `kube/`) provides:
-
-* A Deployment with configurable replica count.
-* A Service of type `NodePort` (default port `30001`) or `LoadBalancer` for cloud environments.
-* A Secret (`pr-reviewer-env`) that stores all `.env` values, including Gitea tokens and LLM credentials.
-* An optional HorizontalPodAutoscaler that scales based on CPU utilisation.
-
-The CI pipeline (`.gitea/workflows/build_push.yml`) automatically builds a multi‑arch Docker image, pushes it to the configured registry, and applies the Kubernetes manifests.  
-
-### Resource considerations  
-
-* **CPU** – The LLM inference dominates CPU usage. When using a hosted provider, the container’s CPU footprint is modest (mostly for Semgrep/Trivy). With a local model, allocate at least 4 vCPUs and 8 GB RAM.
-* **Memory** – Each review crew consumes roughly 200 MB of RAM; the summariser adds another 150 MB. The total stays under 1 GB for typical PR sizes.
-* **Storage** – The image size is ~1.2 GB (including all scanning tools). Persistent storage is not required unless audit logging is enabled.  
-
-## Configuration details  
-
-All runtime options are supplied via environment variables. The most important groups are:
-
-| Variable | Required? | Description |
-|---|---|---|
-| `LLM_PROVIDER` | Yes | `openai`, `anthropic`, or `ollama`. |
-| `LLM_MODEL` | Yes | Model identifier (e.g., `gpt-4`). |
-| `LLM_API_KEY` | Conditional | API key for hosted providers. |
-| `ACCESS_GITEA_URL` | Yes | Base URL of the Gitea instance. |
-| `ACCESS_GITEA_TOKEN` | Yes | Personal access token with repository read scope. |
-| `ACCESS_GITEA_SECRET` | No | Webhook secret for HMAC verification. |
-| `TOTAL_FLOW_TIMEOUT` | No (default 600) | Max seconds for the whole review pipeline. |
-| `PER_CREW_TIMEOUT` | No (default 300) | Max seconds per individual crew. |
-| `LOG_LEVEL` | No (default `INFO`) | Python logging verbosity. |
-
-Additional optional variables allow overriding default review guidelines (`CODE_REVIEW_GUIDELINES`, `SECURITY_REVIEW_GUIDELINES`, `INFRA_REVIEW_GUIDELINES`) by pointing to markdown files stored in the container or mounted via a volume.  
-
-## Operational considerations  
-
-### Monitoring  
-
-FastAPI’s built‑in metrics can be exposed via `/metrics` (Prometheus format). Key metrics include:
-
-* `pr_review_requests_total`
-* `pr_review_duration_seconds`
-* `crew_timeout_total` (per crew)
-* `llm_api_errors_total`
-
-Collecting these metrics enables alerting on abnormal latency spikes, which often indicate upstream LLM throttling or unusually large diffs.  
-
-### Logging  
-
-Structured JSON logs are emitted by default, containing fields such as `request_id`, `pr_id`, `crew`, and `severity`. When integrated with a log aggregation platform (e.g., Loki), operators can trace the lifecycle of a single PR review from receipt to comment posting.  
-
-### Security  
-
-* **Secret management** – Store all tokens and API keys in a secret manager (Kubernetes Secrets, HashiCorp Vault, or Azure Key Vault). Never commit `.env` files to source control.
-* **Network isolation** – If using a local LLM, keep the Ollama container on a private network and restrict outbound internet access.
-* **Rate limiting** – The service respects the `X-RateLimit-Remaining` header from hosted LLM APIs and backs off automatically to avoid hitting provider quotas.  
-
-## Extending to other CI/CD platforms  
-
-While the reference implementation focuses on Gitea, the architecture encourages reuse:
-
-1. **Create an adapter** – Implement a small FastAPI route that accepts GitHub `pull_request` webhook payloads, validates the signature (`X-Hub-Signature-256`), and maps fields to the internal PR model.
-2. **Reuse the core flow** – Forward the transformed payload to the existing `/api/v1/review` endpoint. No changes to the review crews are required.
-3. **Deploy the new route** – Add the new route to the FastAPI app, update the Docker image, and configure the external webhook in the target platform.
-
-Because the review logic is decoupled from the webhook source, teams can support multiple providers simultaneously, each posting its own comment to the respective PR.  
-
-## Development workflow  
-
-Contributors who wish to enhance PR Reviewer can follow these steps:
-
-```bash
-# Clone the repository
-git clone https://git.aridgwayweb.com/armistace/pr_reviewer.git
-cd pr_reviewer
-
-# Install development dependencies
-uv pip install -e ".[dev]"
-
-# Run the test suite
-pytest tests/
-
-# Start the server locally for rapid iteration
-uvicorn src.pr_reviewer.main:app --reload
-```
-
-The project uses **uv** for isolated virtual environments, **pytest** for unit and integration tests, and **ruff** for linting. CI pipelines enforce 100 % test coverage and run static analysis on every pull request.  
-
-### Adding a new review tool  
-
-To incorporate an additional analysis tool (e.g., a custom static analyser), developers should:
-
-1. Write a thin wrapper that converts the tool’s output into the MCP schema.
-2. Register a new crew in `crews/` that invokes the wrapper.
-3. Update the orchestration flow (`flow.py`) to include the new crew in the parallel execution block.
-4. Add corresponding unit tests that mock the tool’s output and verify correct MCP conversion.  
-
-## Testing and quality assurance  
-
-PR Reviewer’s reliability hinges on three testing layers:
-
-* **Unit tests** – Validate each crew’s MCP conversion logic, LLM prompt generation, and webhook parsing.
-* **Integration tests** – Spin up a temporary Docker Compose environment with a mock Gitea server, submit a synthetic PR payload, and assert that the final markdown report contains expected sections.
-* **End‑to‑end tests** – Deploy the Helm chart to a disposable Kubernetes namespace, trigger a real Gitea webhook, and verify that the comment appears on the PR with correct formatting.
-
-All tests run in CI on every push, and failures block merges.  
-
-## Community and contributions  
-
-The project is deliberately open‑source, hosted on a self‑managed Gitea instance. Contributors are encouraged to:
-
-* **Open issues** – Report bugs, request new review domains, or suggest LLM prompt improvements.
-* **Submit pull requests** – Follow the contribution guidelines in `CONTRIBUTING.md`, which outline code style, testing requirements, and documentation standards.
-* **Share custom guidelines** – Teams can publish repository‑specific markdown files (e.g., `code_review.md`) that the summariser will automatically honour.  
-
-Because the tool is designed for private deployment, there is no central SaaS offering. Instead, the community benefits from shared Docker images, Helm charts, and a growing catalogue of custom rule sets that can be forked and adapted.  
-
-## Limitations and future directions  
-
-### Current constraints  
-
-* **LLM dependence** – The quality of the final summary is directly tied to the underlying model’s capabilities. Low‑capacity models may produce vague recommendations.
-* **Static analysis scope** – While Semgrep, Trivy, Hadolint and Checkov cover many common languages and platforms, niche tech stacks (e.g., Rust, Terraform Cloud) require additional adapters.
-* **No built‑in CI/CD orchestration** – PR Reviewer focuses on the review step; it does not enforce merge policies or gate deployments. Teams must integrate the API into their existing pipelines.  
-
-### Planned enhancements  
-
-1. **Model‑agnostic prompt optimisation** – Research into dynamic prompt templates that adapt to the strengths of each LLM provider.
-2. **Feedback loop** – Capture developer reactions to the AI suggestions (e.g., thumbs up/down) and use them to fine‑tune future prompts.
-3. **Extended platform support** – Official adapters for GitHub Actions, GitLab CI, and Azure DevOps.
-4. **Cache layer** – Introduce a Redis‑backed cache for repeated scans of unchanged files, reducing compute cost on large monorepos.
-5. **Policy as code** – Allow organisations to define review policies in a declarative YAML format that the summariser can reference, enabling compliance‑first workflows.  
-
-## Conclusion  
-
-PR Reviewer demonstrates that AI‑driven code quality, security, and infrastructure analysis can be delivered as a self‑hosted, vendor‑neutral service without sacrificing flexibility or control. By leveraging CrewAI’s flow orchestration, MCP’s structured data exchange, and a modular architecture, the system provides consistent, actionable feedback across multiple domains while remaining easy to extend and integrate into existing CI/CD pipelines.  
-
-For teams that value privacy, customisation, and the ability to run sophisticated analysis on modest hardware, PR Reviewer offers a pragmatic path forward. The open‑source nature invites collaboration, and the clear separation between tooling, LLM inference and summarisation ensures that future improvements—whether in scanning capabilities or language model performance—can be adopted with minimal friction.  
-
-Give it a spin, contribute a rule set, or simply use it to offload the routine parts of your PR workflow. In doing so, you’ll free up senior engineers to focus on the strategic decisions that truly move software forward.  

src/content/zen_browser__is_it_the_new_browser_for_me.md

@@ -1,228 +0,0 @@
-Title: Zen Browser - Is it new browser for me?  
-Date: 2026-05-03  
-Modified: 2026-05-03  
-Category: Browsers  
-Tags: firefox, zen-browser, privacy, open-source, alternatives, ai_content, not_human_content  
-Slug: zen-browser-new-browser-for-me  
-Authors: Andrew Ridgway... and friends - glm-5.1, nemotron-3-nano, gemma4, deepseek-v4-flash
-Summary: A deep dive into Zen Browser, its Firefox‑based architecture, privacy‑focused design, and whether it can replace your current browser in a Chromium‑dominated world.  
-
-## 1. Why the browser matters today  
-
-The web is no longer a quiet place where you could pop a page, read a story, and close the tab without a second thought. In 2026 the internet is saturated with AI‑generated content, relentless push notifications, and a market that has coalesced around a single rendering engine: Chromium. Chrome, Edge, Brave, Vivaldi, Opera and even the newer Arc all sit on the same Blink‑based foundation. That homogeneity brings convenience—websites only need to be tested once—but it also creates a monoculture where a single corporate decision can ripple through the entire ecosystem.
-
-For many developers and power users this is uncomfortable. The same engine means the same telemetry, the same default data‑sharing practices, and the same attack surface. It also means that innovation at the engine level is effectively a zero‑sum game: if Google decides to deprecate a web standard, every Chromium browser follows suit. The result is a web that feels increasingly curated by a single entity.
-
-I have spent the last decade fighting this trend. At home and work I keep Firefox as my default on the desktop and on my phone, mainly out of principle rather than passion. The browser feels like a relic in a world that worships speed and AI‑driven UI tricks, yet it remains the most trustworthy open‑source option I know.
-
-Enter Zen Browser, a project that promises to give Firefox a fresh coat of paint while preserving its core values. The question is whether Zen can be the “new browser for me” without forcing me to abandon the ecosystem I have built around Firefox.
-
----
-
-## 2. The state of the browser market in 2026  
-
-Before we can judge Zen on its own merits, it helps to understand the broader landscape.
-
-| Browser | Engine | Open‑source? | Mobile version | Sync ecosystem |
-|---------|--------|---------------|----------------|----------------|
-| Chrome  | Blink  | No (proprietary) | Android, iOS (WebView) | Google Account |
-| Edge    | Blink  | Partially (Chromium core) | Android, iOS | Microsoft Account |
-| Brave   | Blink  | Yes (MIT) | Android, iOS | Brave Sync |
-| Vivaldi | Blink  | Yes (GPL) | Android (WebView) | Vivaldi Sync |
-| Arc     | Blink  | No (closed) | None (desktop only) | Arc Cloud |
-| Firefox | Gecko | Yes (MPL) | Android, iOS | Firefox Sync |
-| **Zen** | Gecko (fork) | Yes (MPL) | **None** (desktop only) | Firefox Sync (built‑in) |
-
-The table shows that Zen is the only desktop‑only browser that still runs on Gecko while offering a radically different UI. Its lack of a mobile client is a drawback, but the built‑in Firefox Sync mitigates the inconvenience by allowing seamless hand‑off to the regular Firefox mobile app.
-
-Another trend worth noting is the rise of “no‑Google” browsers. Users increasingly value a browsing experience that does not automatically send telemetry to Google, nor embed Google services by default. Zen positions itself squarely in that niche, advertising a “no‑Google” promise and disabling telemetry out of the box.
-
----
-
-## 3. Zen’s technical foundation  
-
-### 3.1 A true Firefox fork  
-
-Zen is not a “Firefox‑inspired” project that re‑implements features on top of Chromium. It is a **fork of the Firefox source code**, meaning it inherits the Gecko rendering engine, the SpiderMonkey JavaScript engine, and the same security model that has protected Firefox users for over a decade. The developers have taken the Firefox codebase, stripped away the default UI, and rebuilt the chrome (the browser UI, not the Chrome engine) to match a minimalist aesthetic.
-
-Because it is a fork, Zen benefits from every upstream security patch that Mozilla releases. When Mozilla pushes a fix for a memory‑corruption bug, Zen can merge it with minimal effort. Conversely, any regression introduced by Zen’s UI layer can be isolated without affecting the core engine.
-
-### 3.2 Firefox Sync baked in  
-
-One of the biggest friction points for any new browser is data migration. Zen solves this by integrating Firefox Sync directly into its startup flow. When you launch Zen for the first time you are prompted to sign in with your existing Firefox account. The browser then pulls in:
-
-- Bookmarks
-- Saved passwords (encrypted with your Firefox master password)
-- Open tabs
-- History
-- Preferences (where applicable)
-
-The result is a seamless transition: you can keep your existing workflow, extensions, and saved credentials without manual export/import. This is especially valuable for users who have invested years of curation into their Firefox profile.
-
-### 3.3 Open‑source ethos  
-
-Zen’s source lives on GitHub under the Mozilla Public License 2.0, the same license that governs Firefox. The repository is public, issues are triaged openly, and contributions are welcomed from anyone with the requisite skill set. For developers who like to peek under the hood, the code is fully auditable. The project also provides pre‑built binaries for Windows, macOS and Linux, as well as Flatpak, AppImage and tarball options for the Linux crowd.
-
----
-
-## 4. User experience: the “Zen” in Zen Browser  
-
-### 4.1 Minimalist UI  
-
-The most striking aspect of Zen is its **Zen Mode** (also called Compact Mode). When you open a new window you are greeted with a blank canvas that contains only the web page. The traditional tab bar, bookmarks toolbar, and extension icons are hidden by default. Hovering near the top edge reveals a thin, unobtrusive sidebar that contains the address bar, a minimal set of navigation controls, and a button to toggle the sidebar itself.
-
-This design is deliberately anti‑clutter. It respects the user’s attention by removing visual noise, allowing the content to take centre stage. For developers who spend hours reading documentation or for writers who need a distraction‑free environment, this mode feels like a digital equivalent of a quiet study.
-
-### 4.2 Vertical tabs and workspaces  
-
-Zen replaces the classic horizontal tab strip with **vertical tabs** that sit on the left side of the window. Each tab is represented by its favicon and title, and you can drag‑and‑drop to reorder them. The vertical layout pairs naturally with the sidebar, creating a “pane‑like” feel that many tiling‑window‑manager enthusiasts will recognise.
-
-Beyond simple tabs, Zen introduces **workspaces**. A workspace is a collection of tabs that can be switched with a single keyboard shortcut (Ctrl+Alt+←/→ by default). This allows you to separate, for example, work‑related sites from personal browsing without opening a new window. The workspace concept mirrors the way developers use virtual desktops on their operating system, bringing that mental model into the browser.
-
-### 4.3 Split view  
-
-Another productivity‑focused feature is **split view**. By dragging a tab to the right edge of the window, Zen automatically creates a side‑by‑side layout where two pages share the same window. This is handy for comparing documentation with a live site, watching a tutorial while coding, or simply keeping a chat window open alongside a news feed.
-
-The split view is implemented using the same rendering process for both panes, so performance remains consistent. The UI automatically resizes when you move the divider, and you can close either pane independently.
-
-### 4.4 Keyboard‑first philosophy  
-
-Zen assumes you will spend most of your time navigating with the keyboard. The default shortcuts are intentionally similar to those you already know from Firefox and other browsers:
-
-| Shortcut | Action |
-|----------|--------|
-| Ctrl + T | New tab |
-| Ctrl + N | New window |
-| Ctrl + W | Close tab |
-| Ctrl + Shift + T | Reopen closed tab |
-| Ctrl + L | Focus address bar |
-| Ctrl + Alt + ←/→ | Switch workspace |
-| Ctrl + Shift + S | Toggle split view |
-| Ctrl + B | Toggle sidebar |
-| Ctrl + / | Open command palette (search commands) |
-
-Because the UI is hidden most of the time, these shortcuts become the primary way to interact with the browser. Users quickly develop muscle memory, and the result is a faster, more fluid browsing experience.
-
-### 4.5 Extension compatibility  
-
-Since Zen runs on Gecko, it supports the **Mozilla Add‑ons ecosystem** out of the box. Popular extensions such as uBlock Origin, Bitwarden, Dark Reader, and the myriad of developer tools work without modification. The only caveat is that extensions that rely on Chrome‑specific APIs will not function, but those are rare in the Firefox world.
-
-The developers have also introduced a **mods system** that allows community‑created UI tweaks, themes, and custom CSS. This is similar to the old Firefox “userChrome.css” approach but packaged in a more discoverable way. Users can browse the Zen Mods repository, install a theme with a single click, and have the browser instantly re‑skin itself.
-
----
-
-## 5. Privacy, security and the “no‑Google” promise  
-
-### 5.1 Telemetry disabled by default  
-
-One of the most common criticisms of modern browsers is the amount of telemetry they ship. Zen disables all telemetry at launch. No usage data is sent to the Zen developers unless you explicitly opt‑in via the Settings panel. This aligns with the privacy‑first ethos that attracted many to Firefox in the first place.
-
-### 5.2 No bundled Google services  
-
-Chrome and its Chromium siblings ship with Google services baked into the browser: Safe Browsing, Google Translate, automatic sign‑in, and more. Zen strips all of these out. The only external services it contacts are Mozilla’s update servers (for security patches) and the Firefox Sync servers (for data sync). There is no default integration with Google Analytics, no automatic Google account sign‑in, and no built‑in Widevine DRM.
-
-### 5.3 DRM and media playback  
-
-Because Zen chooses not to include proprietary DRM modules, it cannot play Widevine‑protected streams (Netflix, Disney+, etc.) out of the box. Users who need this functionality must fall back to Firefox or a Chromium‑based browser for those sites. The developers have been transparent about this limitation, and many users accept it as a reasonable trade‑off for a cleaner, more private browsing experience.
-
-### 5.4 Security updates  
-
-Zen inherits Firefox’s rapid security‑patch cadence. When Mozilla releases a critical fix, the Zen maintainers merge it into the next release within days. The project also runs its own automated build pipeline that signs binaries, ensuring that users receive authentic updates.
-
----
-
-## 6. Performance and stability  
-
-### 6.1 Benchmarks vs real‑world use  
-
-Synthetic benchmarks (e.g., Speedometer 3) show Zen scoring slightly lower than vanilla Firefox—around 5‑7 % slower—primarily due to the additional UI layer. In practice, the difference is imperceptible for everyday tasks such as browsing news sites, reading documentation, or coding. The vertical tab and workspace features add negligible overhead because they are UI constructs rather than rendering changes.
-
-### 6.2 Memory footprint  
-
-Zen’s memory usage is comparable to Firefox’s default profile. The hidden UI reduces the number of active UI elements, which can actually lower RAM consumption when many tabs are open. Users have reported being able to keep 30‑40 tabs open without the system slowing down, a figure that matches or exceeds most Chromium browsers on the same hardware.
-
-### 6.3 Stability track record  
-
-Since its first stable release (v1.0) in early 2025, Zen has maintained a steady release cadence—approximately one minor version every six weeks. Crash reports have steadily declined as the codebase matures. The most common issues reported are related to split view quirks on certain Linux window managers, but these are being addressed in the upcoming 1.21 release.
-
----
-
-## 7. Limitations and trade‑offs  
-
-| Limitation | Impact | Mitigation |
-|------------|--------|-------------|
-| No mobile app (Android/iOS) | Cannot browse Zen‑only UI on phone | Use Firefox mobile with Sync to keep bookmarks, passwords, and open tabs |
-| No built‑in Widevine DRM | Cannot stream Netflix/Disney+ directly | Use a Chromium browser for DRM‑protected services |
-| Smaller development team | Potential risk of abandonment | Community contributions, open‑source transparency |
-| Limited CLI documentation | Advanced users may lack command‑line options | Most Firefox CLI flags work; community can extend docs |
-
-These constraints are not deal‑breakers for many power users. The ability to keep a consistent workflow across desktop devices, combined with the privacy benefits, outweighs the lack of a native mobile client for a sizable portion of the audience.
-
----
-
-## 8. Getting started with Zen  
-
-1. **Download** – Visit the official site (https://zen-browser.app) and choose the installer for your OS. Linux users can pick Flatpak, AppImage, or a tarball.  
-2. **Install** – Run the installer; on Windows and macOS the process is straightforward. Linux users may need to make the AppImage executable (`chmod +x`).  
-3. **Sign in** – On first launch, click “Sign in with Firefox” and enter your Mozilla account credentials. This will pull in your existing data.  
-4. **Configure** – Open Settings → Privacy to verify telemetry is disabled. Adjust shortcuts under Keyboard → Shortcuts if you prefer different key bindings.  
-5. **Explore** – Try Zen Mode (Ctrl + /), enable vertical tabs, create a workspace, and experiment with split view.  
-6. **Install extensions** – Visit addons.mozilla.org from within Zen and add your favourite tools.  
-7. **Join the community** – The Discord server and GitHub Discussions are active places to ask questions, report bugs, or suggest features.
-
----
-
-## 9. How Zen compares to other browsers  
-
-| Feature | Zen | Firefox (standard) | Chrome | Brave | Vivaldi |
-|---------|-----|--------------------|--------|-------|---------|
-| Engine | Gecko (fork) | Gecko | Blink | Blink | Blink |
-| UI paradigm | Vertical tabs, workspaces, Zen Mode | Traditional tab bar | Minimalist but Chrome‑centric | Similar to Chrome with added shields | Highly customizable |
-| Default telemetry | Disabled | Enabled (opt‑out) | Enabled | Enabled (opt‑out) | Enabled |
-| Google services | None | None | Integrated | Integrated | Integrated |
-| Mobile app | None (use Firefox) | Yes | Yes | Yes | Yes |
-| DRM support | No | No (requires separate plugin) | Yes | Yes | Yes |
-| Open‑source | Yes (MPL) | Yes (MPL) | No (proprietary) | Yes (MIT) | Yes (GPL) |
-| Extension ecosystem | Mozilla Add‑ons | Mozilla Add‑ons | Chrome Web Store | Chrome Web Store | Chrome Web Store |
-
-Zen occupies a unique niche: it offers a radically different UI while staying within the Firefox ecosystem. For users who love Firefox’s privacy stance but crave a fresh visual experience, Zen is the only option that satisfies both criteria without resorting to Chromium.
-
----
-
-## 10. Who should give Zen a try?  
-
-- **Privacy‑conscious users** who want a browser that does not ship Google telemetry by default.  
-- **Power users** who rely heavily on keyboard navigation, vertical tabs, and workspace separation.  
-- **Developers** who already have a Firefox profile and want to keep their bookmarks, passwords, and extensions intact while experimenting with a new UI.  
-- **Linux enthusiasts** who appreciate open‑source software and the ability to install via Flatpak or AppImage.  
-- **Anyone tired of the Chromium monoculture** and looking for a viable alternative that still renders modern web standards correctly.
-
-Conversely, Zen may not be ideal for:
-
-- Users who need **DRM‑protected streaming** on a daily basis.  
-- Mobile‑first users who expect a seamless browser experience across phone and tablet.  
-- Organizations that require **same‑day security patches** for a large fleet of machines (Chromium browsers often receive patches faster due to corporate backing).  
-
----
-
-## 11. The future of Zen  
-
-The browser market has a notorious “scrap heap” where ambitious projects disappear after a few years. Zen’s survival hinges on three factors:
-
-1. **Community involvement** – Because the code is open, contributors can add features, fix bugs, and keep the project alive even if the core team shrinks.  
-2. **Sustainable funding** – The project currently relies on donations and occasional sponsorships. A steady revenue stream would allow dedicated developers to work full‑time.  
-3. **Feature roadmap** – Delivering a mobile client, adding optional DRM support, and refining split view stability are on the public roadmap. Hitting these milestones will broaden Zen’s appeal.
-
-If these conditions are met, Zen could become a long‑term pillar of the non‑Chromium ecosystem, offering a viable, privacy‑first alternative for years to come.
-
----
-
-## 12. Final thoughts  
-
-Zen Browser is more than a cosmetic overhaul of Firefox; it is a statement that the web does not have to be dominated by a single engine and a single corporate agenda. Its minimalist UI, vertical tabs, workspaces, and split view provide a fresh workflow that respects the user’s attention. The seamless integration with Firefox Sync means you can adopt Zen without losing the data you have painstakingly built up over years.
-
-The trade‑offs—no mobile client, no built‑in DRM—are real, but they are transparent and can be worked around. For anyone who values privacy, open‑source principles, and a keyboard‑first experience, Zen is worth a serious look.
-
-In a world where AI‑generated noise threatens to drown out thoughtful browsing, Zen offers a quiet corner where the page itself can finally be heard. Give it a spin, set up your workspaces, and see whether it becomes the new browser for you.
-
----

src/pelicanconf.py

@@ -6,7 +6,7 @@ SITENAME = "Andrew Ridgway's Blog"
 SITEURL = 'https://blog.aridgwayweb.com'
 THEME = 'themes/cleanblog'
 PATH = 'content'
-HEADER_COVER = 'https://blog.aridgwayweb.com/images/Tech-Desktop-Wallpaper-35697.jpg'
+HEADER_COVER = 'https://wallpaperaccess.com/full/3239444.jpg'
 TIMEZONE = 'Australia/Brisbane'
 COLOR_SCHEME_CSS = 'tomorrow.css'
 DEFAULT_LANG = 'en'

src/themes/cleanblog/templates/article.html

@@ -33,7 +33,7 @@
     {% if article.header_cover %}
         <header class="intro-header" style="background-image: url('{{ article.header_cover }}')">
     {% else %}
-        <header class="intro-header" style="background-image: url('{{ SITEURL }}/{{ THEME_STATIC_DIR }}/images/post-bg.png')">
+        <header class="intro-header" style="background-image: url('{{ SITEURL }}/{{ THEME_STATIC_DIR }}/images/post-bg.jpg')">
     {% endif %}
         <div class="container">
             <div class="row">