# docker-osx - Doramagic AI Context Pack

> Positioning: a pre-install experience and judgment asset. It helps the host AI get off to a good start, but it does not mean the project has already been installed, run, or validated.

## Sufficiency Principle

- **Sufficiency over compression**: The AI Context Pack should be sufficient for the host AI to understand the project's value, capability boundaries, entrypoints, risks, and evidence sources before starting work; it may be layered, but it does not aim for the shortest possible summary.
- **Compression policy**: Compress only noise and duplication, never context that affects judgment or the quality of the work.

## How the Host AI Should Use This

You are reading the AI Context Pack that Doramagic compiled for docker-osx. Treat it as pre-work context: help the user understand who it fits, what it can do, how to start, what must be verified after install, and where the risks are. Do not claim that you have already installed, run, or executed the target project.

## Claim Consumption Rules

- **Fact source**: Repo Evidence + Claim/Evidence Graph; the Human Wiki only supplies salience, terminology, and narrative structure.
- **Minimum status for a fact**: `supported`
- `supported`: May be used as a project fact, but the answer must cite the claim_id and evidence path.
- `weak`: Usable only as a low-confidence lead; the user must be asked to keep verifying.
- `inferred`: Usable only for risk notes or open questions; must not be packaged as a project fact.
- `unverified`: Must not be used as fact; state clearly that evidence is insufficient.
- `contradicted`: Must show the conflicting sources and must not force a single version on the user's behalf.

## Who It Fits Best

- **AI researchers or builders of research-oriented Agents**: The README clearly centers on research, experiment, or paper workflows. Evidence: `README.md` Claim: `clm_0002` supported 0.86

## What It Can Do

- **Command-Line Startup or Install Flow** (Verify after install): The project documentation contains runnable commands; real use requires running them in a local or host environment. Evidence: `README.md` Claim: `clm_0001` supported 0.86

## How to Start

- `git clone https://github.com/corellium/usbfluxd.git` Evidence: `README.md` Claim: `clm_0003` supported 0.86

## Continue-or-Stop Decision Card

- **Current recommendation**: Sandbox trial only
- **Why**: The project has signals of install commands, host configuration, or local writes; do not go straight into your primary environment—trial it in isolation first.

### 30-Second Read

- **What to do now**: Sandbox trial only
- **Minimum safe next step**: Run Prompt Preview first; if you still want to install, trial only in an isolated environment
- **Do not trust yet**: Real output quality cannot be trusted before install.
- **Continuing will touch**: Command execution, Local environment or project files, Host AI context

### What You Can Trust Now

- **Target-audience signal: AI researchers or builders of research-oriented Agents** (supported): Backed by a supported claim or project evidence, but that still is not the same as real install results. Evidence: `README.md` Claim: `clm_0002` supported 0.86
- **Capability exists: Command-Line Startup or Install Flow** (supported): You can trust that the project contains signals of this capability; whether it fits your specific task still needs trial or after-install verification. Evidence: `README.md` Claim: `clm_0001` supported 0.86
- **There are Quick Start / install-command signals** (supported): You can trust that the docs mention a startup or install entrypoint; do not run it directly in your primary environment because of that. Evidence: `README.md` Claim: `clm_0003` supported 0.86

### What You Cannot Trust Yet

- **Real output quality cannot be trusted before install.** (unverified): Prompt Preview can only show how it guides you; it cannot prove result quality in the real project.
- **Host AI version compatibility cannot be trusted before install.** (unverified): Host loading rules and version differences across Claude, Cursor, Codex, Gemini, and others must be verified in a real environment.
- **That it will not pollute your existing host AI's behavior cannot be trusted directly.** (inferred): Skill, plugin, and AGENTS/CLAUDE/GEMINI instructions may change the host AI's default behavior.
- **Safe rollback cannot be assumed by default.** (unverified): Unless the project clearly provides uninstall and recovery instructions, verify in an isolated environment first.
- **After a real install, is it compatible with the user's current host AI version?** (unverified): Compatibility can only be verified in the actual host environment.
- **Does the project's output quality meet the user's specific task?** (unverified): The pre-install preview can only show flow and boundaries; it cannot replace real evaluation.
- **Do the install commands require network access, permissions, or global writes?** (unverified): This affects install risk in both enterprise and personal environments. Evidence: `README.md`

### What Continuing Will Touch

- **Command execution**: Package managers, network downloads, the local plugin directory, project config, or the user's home directory. Why: Running the very first command can already change your environment; decide whether it is worth running first. Evidence: `README.md`
- **Local environment or project files**: Install results, plugin caches, project config, or local dependency directories. Why: The write scope and rollback path cannot be proven before install and need isolated verification. Evidence: `README.md`
- **Host AI context**: The AI Context Pack, Prompt Preview, Skill routing, risk rules, and project facts. Why: Importing context affects the host AI's later judgment, so avoid packaging unverified items as facts.

### Minimum Safe Next Steps

- **Run Prompt Preview first**: Use a pre-install interactive trial to judge whether the way of working fits; it needs no authorization or environment change. (applies when: Applies to any project, especially when output quality is unknown.)
- **Trial-install only in an isolated directory or a test account**: Avoid letting install commands pollute your primary host AI, real projects, or home directory. (applies when: When there are signals of command execution, plugin config, or local writes.)
- **After install, verify just one minimal task**: Verify loading, compatibility, output quality, and rollback first, then decide whether to use it deeply. (applies when: When moving from a trial into a real workflow.)

### Exit Plan

- **Preserve the pre-install state**: Record the original host config and project state so you can later judge whether it is recoverable.
- **Record the install commands and written paths**: Without clear uninstall instructions, you at least need to know which directories or configs to clean up manually.
- **If there is no rollback path, do not enter your primary environment**: No rollback is a blocker before continuing; do not proceed on trust or luck.

## What Can Only Be Previewed

- Explain who the project fits and what it can do
- Demonstrate a typical conversation flow based on project docs
- Help the user decide whether it is worth installing or researching further

## What Must Be Verified After Install

- Actually installing the Skill, plugin, or CLI
- Running scripts, modifying local files, or accessing external services
- Verifying real output quality, performance, and compatibility

## Boundary & Risk Decision Card

- **Mistaking the pre-install preview for a real run**: The user may overestimate how much configuration, permission, and compatibility verification the project has already done. Mitigation: Clearly separate prompt_preview_can_do from runtime_required. Claim: `clm_0004` inferred 0.45
- **Command execution will modify the local environment**: Install commands may write to the user's home directory, the host plugin directory, or project configuration. Mitigation: Run in an isolated environment or a test account first. Evidence: `README.md` Claim: `clm_0005` supported 0.86
- **To confirm**: After a real install, is it compatible with the user's current host AI version?. Why: Compatibility can only be verified in the actual host environment.
- **To confirm**: Does the project's output quality meet the user's specific task?. Why: The pre-install preview can only show flow and boundaries; it cannot replace real evaluation.
- **To confirm**: Do the install commands require network access, permissions, or global writes?. Why: This affects install risk in both enterprise and personal environments.

## Pre-Work Working Context

### Loading Order

- First read how_to_use.host_ai_instruction to establish the boundaries of this pre-install judgment asset.
- Read claim_graph_summary to confirm facts come from the Claim/Evidence Graph, not the Human Wiki narrative.
- Then read intended_users, capabilities, and quick_start_candidates to judge whether the user is a match.
- When you need to carry out a concrete task, check role_skill_index first, then evidence_index.
- For real install, file modification, network access, performance, or compatibility questions, turn to risk_card and boundaries.runtime_required.

### Task Routes

- **Command-Line Startup or Install Flow**: State that this is an after-install capability first, then give a pre-install checklist. Boundary: Must be verified after a real install or run. Evidence: `README.md` Claim: `clm_0001` supported 0.86

### Context Scale

- Total files: 38
- Important-file coverage: 32/38
- Evidence index entries: 32
- Role / Skill entries: 7

### Handling Insufficient Evidence

- **missing_evidence**: State that evidence is insufficient and ask the user for the target file, a README section, or after-install verification records; do not fill in facts.
- **out_of_scope_request**: State that the task is beyond the current AI Context Pack's evidence scope and suggest the user check the Human Manual or verify after a real install.
- **runtime_request**: Provide a pre-install checklist and command sources, but do not run commands for the user or claim they have been run.
- **source_conflict**: Show the conflicting sources side by side, mark them as unverified, and do not force a single version.

## Prompt Recipes

### Fit assessment

- Goal: Judge whether this project fits the user's current task.
- Expected output: A fit conclusion, key reasons, evidence citations, what can be previewed before install, what must be verified after install, and a next-step recommendation.

```text
Based on the AI Context Pack for docker-osx, ask me 3 necessary questions first, then judge whether it fits my task. The answer must cover: who it fits, what it can do, what it cannot do, whether it is worth installing, and where the evidence comes from. Every project fact must cite evidence_refs, source_paths, or a claim_id.
```

### Pre-install experience

- Goal: Let the user feel the core workflow before installing, while avoiding packaging the preview as real capability or a marketing promise.
- Expected output: An experience script with boundary labels, an after-install verification checklist, and a cautious recommendation; with no real-run promises or strong marketing language.

```text
Treat docker-osx as a pre-install experience asset, not an already-installed tool or a real runtime environment.

Output exactly four parts:
1. Ask me 3 necessary questions first.
2. Give an "experience script": use the three labels [Previewable before install], [Must verify after install], and [Insufficient evidence] to show how it might guide the workflow.
3. Give an after-install verification checklist: list which capabilities can only be confirmed after a real install, real host loading, and a real project run.
4. Give a cautious recommendation: only "worth researching/trialing further", "add information before deciding", or "not recommended to continue"; do not endorse the project.

Hard boundaries:
- Do not claim you have installed, run, executed tests, modified files, or produced real results.
- Do not write promise-like phrasing such as "auto-adapts", "guarantees passing", "perfect fit", or "strongly recommend installing".
- If you describe how it works after install, you must use a conditional such as "if installed successfully and the host loads the Skill correctly, it might...".
- The experience script may only be written as "example lines / hypothetical flow": use "might ask / might suggest / might show", not "has written, has generated, has passed, is running, is generating".
- Prompt Preview does not hand out install commands; if the user is ready to trial, only prompt them to read Quick Start and the Risk Card first and to verify in an isolated environment.
- Every project fact must come from a supported claim, evidence_refs, or source_paths; inferred/unverified items can only be risks or open questions.

```

### Role / Skill selection

- Goal: Pick the best-matching asset from the project's roles or Skills.
- Expected output: A list of candidate roles or Skills, each with an applicable scenario, evidence paths, risk boundary, and whether after-install verification is needed.

```text
Read role_skill_index and recommend 3-5 of the most relevant roles or Skills for my target task. For each recommendation, state the applicable scenario, likely output, risk boundary, and evidence_refs.
```

### Risk pre-check

- Goal: Identify environment, permission, rule-conflict, and quality risks before installing or adopting.
- Expected output: A checklist of environment, permission, dependency, license, host-conflict, quality risk, and unknown items.

```text
Based on risk_card, boundaries, and quick_start_candidates, give me a pre-install risk pre-check list. Do not run commands for me; only explain what I should check, why, and what impact a failure would have.
```

### Host AI kickoff instruction

- Goal: Turn the project context into a host AI instruction for the start of a conversation.
- Expected output: A pre-work instruction with clear boundaries and clear evidence citations, suitable to copy to a host AI.

```text
Based on the AI Context Pack for docker-osx, generate a pre-work instruction I can paste to my host AI. This instruction must obey not_runtime=true and must not claim the project has been installed, run, or produced real results.
```

## Role / Skill Index

- Indexed 7 role / Skill / project-doc entries.

- **Docker-OSX · Follow @sickcodes on Twitter https://twitter.com/sickcodes** (project_doc): Docker-OSX · Follow @sickcodes on Twitter https://twitter.com/sickcodes Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `README.md`
- **OSX Serial Generator** (project_doc): This folder has been moved to its own repository : Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `custom/README.md`
- **docker-osx** (project_doc): Docker-OSX Helm Chart for Kubernetes. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `helm/README.md`
- **Changelog** (project_doc): Version Date Notes --- --- --- 2021-09-09 Add Monterey 2021-08-27 Add iPhone passthrough OTA! 6.0 2021-08-25 Added naked-auto. Keep kernel at 5.13, even tho it's just for supermin. 5.0 2021-07-25 Retire glibc patch. Retire file command patch. Add bootmenu=on. 2021-07-08 Add CPUID FLAGS to edit the CPUID flags on the fly. 4.4 2021-05-06 Prepare nakedvnc for hub.docker.com. Add ENV BOOT ARGS= to supply additon boot ar… Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `CHANGELOG.md`
- **Credits** (project_doc): The most important part of the project. You. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `CREDITS.md`
- **Frequently Asked Questions** (project_doc): These questions come up regularly, so here are the answers. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `FAQ.md`
- **Install macOS Docker Virtualization** (project_doc): Install macOS Docker Virtualization Setup This walks through setting up QEMU virtualization for running macOS in Docker & Kubernetes Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `helm/INSTALL-QEMU-AND-GPU-IOMMU.md`

## Evidence Index

- Indexed 32 evidence entries.

- **Docker-OSX · Follow @sickcodes on Twitter https://twitter.com/sickcodes** (documentation): Docker-OSX · Follow @sickcodes on Twitter https://twitter.com/sickcodes Evidence: `README.md`
- **OSX Serial Generator** (documentation): This folder has been moved to its own repository : Evidence: `custom/README.md`
- **docker-osx** (documentation): Docker-OSX Helm Chart for Kubernetes. Evidence: `helm/README.md`
- **License** (source_file): GNU GENERAL PUBLIC LICENSE Version 3, 29 June 2007 Evidence: `LICENSE`
- **Changelog** (documentation): Version Date Notes --- --- --- 2021-09-09 Add Monterey 2021-08-27 Add iPhone passthrough OTA! 6.0 2021-08-25 Added naked-auto. Keep kernel at 5.13, even tho it's just for supermin. 5.0 2021-07-25 Retire glibc patch. Retire file command patch. Add bootmenu=on. 2021-07-08 Add CPUID FLAGS to edit the CPUID flags on the fly. 4.4 2021-05-06 Prepare nakedvnc for hub.docker.com. Add ENV BOOT ARGS= to supply additon boot arguments, for example, vmx,rdtscp . Add ENV CPU=Penryn to allow changes to the CPU emulation, for example, Skylake-Client , or see more examples here https://manpages.ubuntu.com/manpages/disco/man7/qemu-cpu-models.7.html . 2021-05-04 Disable arbitrary chown warning 2021-04-27 Fixe… Evidence: `CHANGELOG.md`
- **Credits** (documentation): The most important part of the project. You. Evidence: `CREDITS.md`
- **Frequently Asked Questions** (documentation): These questions come up regularly, so here are the answers. Evidence: `FAQ.md`
- **Install macOS Docker Virtualization** (documentation): Install macOS Docker Virtualization Setup This walks through setting up QEMU virtualization for running macOS in Docker & Kubernetes Evidence: `helm/INSTALL-QEMU-AND-GPU-IOMMU.md`
- **!/usr/bin/docker** (source_file): !/usr/bin/docker / \ / / / \/ / / / / / / / \/ / // / \/ / / / /\ \ / / / / / / / / / / ,< / / / / / / / / / / /\ /\ / / \ / / \ // / / Title: Docker-OSX Mac on Docker Author: Sick.Codes https://twitter.com/sickcodes Version: 6.0 License: GPLv3+ Repository: https://github.com/sickcodes/Docker-OSX Website: https://sick.codes All credits for OSX-KVM and the rest at @Kholia's repo: https://github.com/kholia/osx-kvm OpenCore support go to https://github.com/Leoyzen/KVM-Opencore and https://github.com/thenickdude/KVM-Opencore/ This Dockerfile automates the installation of Docker-OSX It will build a 200GB container. You can change the size using build arguments. This Dockerfile builds on top of t… Evidence: `Dockerfile`
- **!/usr/bin/docker** (source_file): !/usr/bin/docker / \ / / / \/ / / / / / / / \/ / // / \/ / / / /\ \ / / / / / / / / / / ,< / / / / / / / / / / /\ /\ / / \ / / \ // / / :AUTO Title: Docker-OSX Mac on Docker Author: Sick.Codes https://twitter.com/sickcodes Version: 6.0 License: GPLv3+ Repository: https://github.com/sickcodes/Docker-OSX Website: https://sick.codes This Dockerfile is a pre-installed naked installation of Docker-OSX! Default username: user Default password: alpine Take screenshots in the Arch container and display in terminal: scrotcat readme: timezone: UTC/GMT Future versions will navigate the installation process, inside the Dockerfile. Build: docker build -t docker-osx:auto -f Dockerfile.auto . Run: docker… Evidence: `Dockerfile.auto`
- **!/usr/bin/docker** (source_file): !/usr/bin/docker / \ / / / \/ / / / / / / / \/ / // / \/ / / / /\ \ / / / / / / / / / / ,< / / / / / / / / / / /\ /\ / / \ / / \ // / / :NAKED Title: Docker-OSX Mac on Docker Author: Sick.Codes https://twitter.com/sickcodes Version: 6.0 License: GPLv3+ Repository: https://github.com/sickcodes/Docker-OSX Website: https://sick.codes This image won't run unless you supply a disk image using: -v ${PWD}/mac hdd ng.img:/image Take screenshots in the Arch container and display in terminal: scrotcat Build: docker build -t docker-osx:naked -f Dockerfile.naked . Run headless: docker run -it --device /dev/kvm -p 50922:10022 -v ${PWD}/mac hdd ng.img:/image docker-osx:naked Run with display: docker run… Evidence: `Dockerfile.naked`
- **!/usr/bin/docker** (source_file): !/usr/bin/docker / \ / / / \/ / / / / / / / \/ / // / \/ / / / /\ \ / / / / / / / / / / ,< / / / / / / / / / / /\ /\ / / \ / / \ // / / :NAKED-AUTO Title: Docker-OSX Mac on Docker Author: Sick.Codes https://twitter.com/sickcodes Version: 6.0 License: GPLv3+ Repository: https://github.com/sickcodes/Docker-OSX Website: https://sick.codes This Dockerfile needs you to supply a pre-installed installation of Docker-OSX! Visit https://github.com/sickcodes/Docker-OSX for info Evidence: `Dockerfile.naked-auto`
- **Config Custom** (source_file): ACPI Add Comment My custom DSDT Enabled Path DSDT.aml Comment My custom SSDT Enabled Path SSDT-1.aml Comment Read the comment in dsl sample Enabled Path SSDT-ALS0.aml Comment Read the comment in dsl sample Enabled Path SSDT-AWAC-DISABLE.aml Comment Read the comment in dsl sample Enabled Path SSDT-BRG0.aml Comment Read the comment in dsl sample Enabled Path SSDT-EC-USBX.aml Comment Fake EC and USBX Power Enabled Path SSDT-EC.aml Comment Read the comment in dsl sample Enabled Path SSDT-EHCx-DISABLE.aml Comment Read the comment in dsl sample Enabled Path SSDT-IMEI.aml Comment CPU AGPM Plugin=1 Enabled Path SSDT-PLUG.aml Comment Read the comment in dsl sample Enabled Path SSDT-PMC.aml Comment R… Evidence: `custom/config-custom.plist`
- **Config Legacy** (source_file): ACPI Add Comment add DTGP method Enabled Path SSDT-DTGP.aml Comment Fake EC and USBX Power Enabled Path SSDT-EC.aml Comment USB 2.0 Injection Enabled Path SSDT-EHCI.aml Comment CPU AGPM Plugin=1 Enabled Path SSDT-PLUG.aml Delete All Comment Delete CpuPm Enabled OemTableId Q3B1UG0AAAA= TableLength 0 TableSignature U1NEVA== All Comment Delete Cpu0Ist Enabled OemTableId Q3B1MElzdAA= TableLength 0 TableSignature U1NEVA== Patch Comment Q11 to XQ11 Count 1 Enabled Find X1ExMQ== Limit 0 Mask OemTableId Replace WFExMQ== ReplaceMask Skip 0 TableLength 0 TableSignature Comment Q12 to XQ12 Count 1 Enabled Find X1ExMg== Limit 0 Mask OemTableId Replace WFExMg== ReplaceMask Skip 0 TableLength 0 TableSign… Evidence: `custom/config-legacy.plist`
- **Config Nopicker Custom** (source_file): ACPI Add Comment My custom DSDT Enabled Path DSDT.aml Comment My custom SSDT Enabled Path SSDT-1.aml Comment Read the comment in dsl sample Enabled Path SSDT-ALS0.aml Comment Read the comment in dsl sample Enabled Path SSDT-AWAC-DISABLE.aml Comment Read the comment in dsl sample Enabled Path SSDT-BRG0.aml Comment Read the comment in dsl sample Enabled Path SSDT-EC-USBX.aml Comment Fake EC and USBX Power Enabled Path SSDT-EC.aml Comment Read the comment in dsl sample Enabled Path SSDT-EHCx-DISABLE.aml Comment Read the comment in dsl sample Enabled Path SSDT-IMEI.aml Comment CPU AGPM Plugin=1 Enabled Path SSDT-PLUG.aml Comment Read the comment in dsl sample Enabled Path SSDT-PMC.aml Comment R… Evidence: `custom/config-nopicker-custom.plist`
- **Config Nopicker Legacy** (source_file): ACPI Add Comment add DTGP method Enabled Path SSDT-DTGP.aml Comment Fake EC and USBX Power Enabled Path SSDT-EC.aml Comment USB 2.0 Injection Enabled Path SSDT-EHCI.aml Comment CPU AGPM Plugin=1 Enabled Path SSDT-PLUG.aml Delete All Comment Delete CpuPm Enabled OemTableId Q3B1UG0AAAA= TableLength 0 TableSignature U1NEVA== All Comment Delete Cpu0Ist Enabled OemTableId Q3B1MElzdAA= TableLength 0 TableSignature U1NEVA== Patch Comment Q11 to XQ11 Count 1 Enabled Find X1ExMQ== Limit 0 Mask OemTableId Replace WFExMQ== ReplaceMask Skip 0 TableLength 0 TableSignature Comment Q12 to XQ12 Count 1 Enabled Find X1ExMg== Limit 0 Mask OemTableId Replace WFExMg== ReplaceMask Skip 0 TableLength 0 TableSign… Evidence: `custom/config-nopicker-legacy.plist`
- **Generate Specific Bootdisk** (source_file): set -e help text="Usage: ./generate-specific-bootdisk.sh Required options: --model Device model, e.g. 'iMacPro1,1' --serial Device Serial number --board-serial Main Logic Board Serial number MLB --uuid SMBIOS UUID SmUUID --mac-address Used for both the MAC address and to set ROM ROM is lowercased sans any colons Optional options: --width Resolution x axis length in px, default 1920 --height Resolution y axis length in px, default 1080 --kernel-args Additional boot-args --input-plist-url Specify an alternative master plist, via URL --master-plist-url Same as above. --custom-plist Optionally change the input plist. --master-plist Same as above. --output-bootdisk Optionally change the bootdisk… Evidence: `custom/generate-specific-bootdisk.sh`
- **Docker Compose** (source_file): version: '3.4' services: osx: container name: docker-osx build: context: . args: - SIZE=200G - VERSION=10.15.5 image: sickcodes/docker-osx privileged: true environment: - DISPLAY=${DISPLAY:-:0.0} network mode: "host" cap add: - ALL volumes: - /tmp/.X11-unix:/tmp/.X11-unix - /dev:/dev - /lib/modules:/lib/modules - docker-osx data:/home volumes: docker-osx data: name: docker-osx data Evidence: `docker-compose.yml`
- **Chart** (source_file): apiVersion: v1 appVersion: "0.0.1.0" description: "Containerized OSX! Run OSX in a pod, headlessly, or with Xvfb. Test your Apps and master CI/CD processes." name: docker-osx version: 0.2.0 keywords: - docker-osx - mac - macos - qemu - cicd - ios - xnu - darwin - apple - osx Evidence: `helm/Chart.yaml`
- **!/usr/bin/docker** (source_file): !/usr/bin/docker This Dockerfile is to be consumed with the docker osx helm templates. It consumes the Ubuntu image so that OpenCore.qcow2 can be re-generated which happens in Kube itself , not to mention that OSX-KVM was written for Ubuntu. This was not designed to be run in Docker by itself.. very well anyway. Evidence: `helm/Dockerfile`
- **kubernetes.io/ingress.class: nginx** (source_file): replicaCount: 1 image: repository: sickcodes/docker-osx-vnc tag: latest pullPolicy: IfNotPresent userName: ubuntu serverName: server macos: kexts: add: false path: /system image/kexts kextsToAdd: {} configPlist: SystemProductName: iMacPro1,1 MLB: D25338500GUF8YLJA SystemSerialNumber: D25LF7ZEF8JC SystemUUID: 139C94D6-A533-47D2-874F-D365BFD8B047 bootArgs: '-v keepsyms=1 tlbto us=0 vti=9 -wegoff agdpmod=pikera' openCore: rebuild: true boot: timeout: 0 installerSettings: version: 10.15.7 path: /system image/installers qemu: cpu: Penryn,kvm=on,vendor=GenuineIntel,+invtsc,vmware-cpuid-freq=on,+pcid,+ssse3,+sse4.2,+popcnt,+avx,+avx2,+aes,+xsave,+xsaveopt,check softwareGpu: vmware hardwareGpu: ena… Evidence: `helm/values.yaml`
- **!/usr/bin/docker** (source_file): !/usr/bin/docker / \ / / / \/ / / / / / / / \/ / // / \/ / / / /\ \ / / / / / / / / / / ,< / / / / / / / / / / /\ /\ / / \ / / \ // / / VNC EDITION Title: Mac on Docker Docker-OSX VNC EDITION Author: Sick.Codes https://sick.codes/ Version: 3.1 License: GPLv3+ All credits for OSX-KVM and the rest at Kholia's repo: https://github.com/kholia/osx-kvm OpenCore support go to https://github.com/Leoyzen/KVM-Opencore and https://github.com/thenickdude/KVM-Opencore/ This Dockerfile automates the installation of Docker-OSX It will build a 32GB Mojave Disk, you can change the size using build arguments. This file builds on top of the work done by Dhiru Kholia and many others. Build: write down the pass… Evidence: `vnc-version/Dockerfile`
- **!/usr/bin/docker** (source_file): !/usr/bin/docker / \ / / / \/ / / / / / / / \/ / // / \/ / / / /\ \ / / / / / / / / / / ,< / / / / / / / / / / /\ /\ / / \ / / \ // / / :NAKEDVNC Title: Docker-OSX Mac on Docker Author: Sick.Codes https://twitter.com/sickcodes Version: 4.4 License: GPLv3+ Repository: https://github.com/sickcodes/Docker-OSX Website: https://sick.codes This image won't run unless you supply a disk image using: -v ${PWD}/mac hdd ng.img:/image Take screenshots in the Arch container and display in terminal: scrotcat Build: docker build -t docker-osx:nakedvnc -f Dockerfile.nakedvnc . Run headless: docker run -it --device /dev/kvm -p 50922:10022 -v ${PWD}/mac hdd ng.img:/image docker-osx:nakedvnc Run with display:… Evidence: `vnc-version/Dockerfile.nakedvnc`
- **.gitmodules** (source_file): submodule "osx-serial-generator" path = osx-serial-generator url = https://github.com/sickcodes/osx-serial-generator.git Evidence: `.gitmodules`
- **append to csv file** (source_file): set -e help text="Usage: ./generate-unique-machine-values.sh General options: --count, -n, -c Number of serials to generate --model, -m Device model, e.g. 'iMacPro1,1' --csv Optionally change the CSV output filename --tsv Optionally change the TSV output filename --output-dir Optionally change the script output location --width Resolution x axis length in px, default 1920 --height Resolution y axis length in px, default 1080 --kernel-args Additional boot-args --input-plist-url Specify an alternative master plist, via URL --master-plist-url Same as above. --custom-plist Optionally change the input plist. --master-plist Same as above. --output-bootdisk Optionally change the bootdisk filename… Evidence: `custom/generate-unique-machine-values.sh`
- **Opencore Image Ng** (source_file): iso="" img="" cfg="" create work dir function msg { local txt="$1" local bold="\x1b 1m" local normal="\x1b 0m" echo -e "${bold} ${txt}${normal}" } function do cleanup { msg "cleaning up ..." if test "$GUESTFISH PID" != ""; then guestfish --remote -- exit /dev/null 2 &1 true fi sudo rm -rf "$WORK" } WORK="${TMPDIR-/var/tmp}/${0 /}-$$" mkdir "$WORK" exit 1 trap 'do cleanup' EXIT BASE="$ dirname $0 " function print help { cat --img --cfg EOF } while test "$1" != ""; do case "$1" in --iso iso="$2" shift; shift ;; --img img="$2" shift; shift ;; --cfg cfg="$2" shift; shift ;; esac done function fish { echo " " "$@" guestfish --remote -- "$@" exit 1 } function fish init { local format case "$img"… Evidence: `custom/opencore-image-ng.sh`
- **hack** (source_file): def readPlist self,filepath ⋮---- p = plistlib. PlistParser dict rootObject = p.parse f ⋮---- catalogs = { ⋮---- def get default catalog ⋮---- class ReplicationError Exception ⋮---- def cmd exists cmd ⋮---- '''Downloads a URL and stores it in the same relative path on our filesystem. Returns a path to the replicated file.''' ⋮---- hack ⋮---- attempt resume = True ⋮---- path = urlstuff.urlsplit full url 2 relative url = path.lstrip '/' relative url = os.path.normpath relative url ⋮---- local file path = relative url ⋮---- download cmd = 'wget', "-c", "--quiet", "-x", "-nH", full url ⋮---- download cmd = 'wget', "-c", full url ⋮---- download cmd = 'curl', "--silent", "--show-error", "-o", loc… Evidence: `fetch-macOS.py`
- **Artifacthub Repo** (source_file): repositoryID: 7b2e9eeb-620a-43e8-b2cc-24ca33125bfc owners: - name: sickcodes email: info@sick.codes Evidence: `helm/artifacthub-repo.yml`
- **Helm Chart Generate** (source_file): rm -f docker-osx- .tgz helm package . helm repo index . --url https://sickcodes.github.io/Docker-OSX/helm/ Evidence: `helm/helm-chart-generate.sh`
- **Index** (source_file): apiVersion: v1 entries: docker-osx: - apiVersion: v1 appVersion: 0.0.1.0 created: "2021-02-27T04:15:48.784861502Z" description: Containerized OSX! Run OSX in a pod, headlessly, or with Xvfb. Test your Apps and master CI/CD processes. digest: 5a62a9291b1494b9cfaa0708ab7bab9d13cca30adbeaced3d29a5bb6935caac9 keywords: - docker-osx - mac - macos - qemu - cicd - ios - xnu - darwin - apple - osx name: docker-osx urls: - https://sickcodes.github.io/Docker-OSX/helm/docker-osx-0.2.0.tgz version: 0.2.0 generated: "2021-02-27T04:15:48.782073839Z" Evidence: `helm/index.yaml`
- **!/usr/bin/bash** (source_file): !/usr/bin/bash rankmirrors - read a list of mirrors from a file and rank them by speed Generated from rankmirrors.sh.in; do not edit by hand. Copyright c 2009 Matthew Bruenig This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 3 of the License, or at your option any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Pu… Evidence: `rankmirrors`
- **Read the plist file** (source_file): def add kernel patches config path ⋮---- backup path = config path + '.backup' ⋮---- Read the plist file ⋮---- config = plistlib.load f ⋮---- patch1 = { ⋮---- patch2 = { ⋮---- patch exists = False ⋮---- patch exists = True ⋮---- config path = sys.argv 1 ⋮---- success = add kernel patches config path Evidence: `scripts/apply_appleid_kernelpatch.py`

## Rules the Host AI Must Follow

- **Treat this asset as pre-work context, not a runtime environment.**: The AI Context Pack contains only an evidence-backed understanding of the project, not the project's executable state. Evidence: `README.md`, `custom/README.md`, `helm/README.md`
- **When answering the user, distinguish what can be previewed from what can only be verified after install.**: The consumer value of the pre-install experience comes from reducing bad installs and misjudgments, not from pretending to be a real run. Evidence: `README.md`, `custom/README.md`, `helm/README.md`

## Questions the User Should Answer First

- Which host AI or local environment do you plan to use it in?
- Do you just want to experience the workflow first, or are you ready to actually install?
- What matters most to you: install cost, output quality, or conflicts with your existing rules?

## Acceptance Checks

- Every capability claim can be traced back to a file path in evidence_refs.
- AI_CONTEXT_PACK.md does not package previews as a real run.
- The user can understand who it fits, what it can do, how to start, and the risk boundaries within 3 minutes.

---

## Doramagic Context Augmentation

The following sections strengthen the repository context for a host AI. Human Manual data is a reading route, and pitfall notes become operating constraints.

## Human Manual Outline

Usage rule: this is only a reading route and salience signal, not factual authority. Concrete claims must still return to repo evidence or Claim Graph.

Host AI hard rules:
- Do not treat page titles, section order, summaries, or importance values as factual project evidence.
- When explaining the Human Manual outline, state that it is only a reading route or salience signal.
- Capability, installation, compatibility, runtime state, and risk claims must cite repo evidence, source paths, or Claim Graph.

- **Project Overview and System Requirements**: importance `high`
  - source_paths: README.md, FAQ.md, LICENSE, CREDITS.md, CHANGELOG.md
- **Container Images and Supported macOS Versions**: importance `high`
  - source_paths: Dockerfile, Dockerfile.auto, Dockerfile.naked, Dockerfile.naked-auto, vnc-version/Dockerfile
- **OpenCore Configuration, Plist Customization, and Serial Number Generation**: importance `high`
  - source_paths: custom/README.md, custom/config-custom.plist, custom/config-legacy.plist, custom/config-nopicker-custom.plist, custom/config-nopicker-legacy.plist
- **Kubernetes Deployment, Hardware Passthrough, and Troubleshooting**: importance `high`
  - source_paths: docker-compose.yml, helm/README.md, helm/Chart.yaml, helm/values.yaml, helm/Dockerfile

## Repo Inspection Evidence

- repo_clone_verified: true
- repo_inspection_verified: true
- repo_commit: `aa05a2c9a06aabfc8542c1c373ad1ad0af74ede3`
- inspected_files: `Dockerfile`, `README.md`, `docker-compose.yml`

Host AI hard rules:
- Without repo_clone_verified=true, do not claim that the source code has been read.
- Without repo_inspection_verified=true, do not write README, docs, or package-file conclusions as facts.
- Without quick_start_verified=true, do not claim that the Quick Start path has run successfully.

## Doramagic Pitfall Constraints

These rules come from Doramagic discovery, validation, or compilation findings. The host AI must treat them as operating constraints, not background notes.

- No project-specific pitfall log has English-native content; rely on the base pack's risk card and evidence index. Do not invent missing facts.