drydock-sdd 0.1.0__tar.gz

drydock_sdd-0.1.0/.gitignore

@@ -0,0 +1,50 @@
+# Python
+logs/
+__pycache__/
+*.py[cod]
+*.pyo
+*.pyd
+.Python
+*.egg
+*.egg-info/
+dist/
+build/
+.eggs/
+*.whl
+MANIFEST
+
+# Virtual environments
+.venv/
+venv/
+env/
+
+# uv
+.uv/
+
+# Testing
+.pytest_cache/
+.coverage
+htmlcov/
+*.log
+
+# Ruff
+.ruff_cache/
+
+# Editor
+.DS_Store
+.vscode/
+.idea/
+*.swp
+*.swo
+
+# Drydock generated
+prompts/generated/
+
+# Drydock self-host workspace
+targets/
+
+# QuarterDeck local state
+QuarterDeck/data/*.sqlite
+
+# Local project config
+.env

drydock_sdd-0.1.0/LICENSE

@@ -0,0 +1,11 @@
+Copyright (c) 2026 Web Cloud Studio. All rights reserved.
+
+This software and its associated documentation are proprietary and confidential property of
+Web Cloud Studio.
+
+No part of this software or documentation may be copied, reproduced, modified, distributed,
+published, transmitted, sublicensed, sold, used, or otherwise exploited, in whole or in part,
+without prior explicit written permission from Web Cloud Studio.
+
+Possession of a copy does not grant any license or right to use the software or documentation.
+Unauthorized use is strictly prohibited.

drydock_sdd-0.1.0/PKG-INFO

@@ -0,0 +1,240 @@
+Metadata-Version: 2.4
+Name: drydock-sdd
+Version: 0.1.0
+Summary: Governed Blueprint-driven software delivery.
+Project-URL: Homepage, https://github.com/webcloudstudio/Drydock
+Project-URL: Repository, https://github.com/webcloudstudio/Drydock
+Project-URL: Issues, https://github.com/webcloudstudio/Drydock/issues
+Author-email: Ed Barlow <edward.m.barlow@gmail.com>
+License: Proprietary
+License-File: LICENSE
+Keywords: blueprint-driven-development,cli,code-generation,llm,sdd,spec-kit,specification-driven-development
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: License :: Other/Proprietary License
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development :: Code Generators
+Requires-Python: >=3.11
+Requires-Dist: python-dotenv>=1.0
+Provides-Extra: dev
+Requires-Dist: mypy>=1.10; extra == 'dev'
+Requires-Dist: pre-commit>=3.7; extra == 'dev'
+Requires-Dist: pytest-cov>=5.0; extra == 'dev'
+Requires-Dist: pytest>=8.0; extra == 'dev'
+Requires-Dist: ruff>=0.4; extra == 'dev'
+Description-Content-Type: text/markdown
+
+# Drydock
+
+Drydock is an installable Python CLI implementing the governed Drydock Blueprint Methodology
+through **SAIL: Set Up, Arrange, Implement, Loop**.
+
+Copyright (c) 2026 Web Cloud Studio. All rights reserved. See [LICENSE](LICENSE).
+
+---
+
+## Installation
+
+```bash
+uv pip install drydock
+```
+
+Or from source:
+
+```bash
+git clone <repo>
+cd Drydock
+uv venv
+uv pip install -e ".[dev]"
+```
+
+## Working Commands
+
+The following commands are fully implemented:
+
+```bash
+drydock --help
+drydock --version
+
+drydock config show
+drydock config set blueprint_directory <path>
+drydock config set target_directory <path>
+
+drydock init <Target>
+
+drydock validate <Blueprint>
+drydock validate <Blueprint> --verbose
+
+drydock rigging compact <Blueprint> [--all] [--force]
+
+drydock import <Blueprint> <Source> --format markdown
+drydock plan create <Blueprint> <Target>
+drydock build status <Blueprint> <Target>
+```
+
+The planning flow starts with Target initialization, then uses three commands plus QuarterDeck
+approval:
+
+```bash
+drydock init <Target>
+drydock import <Blueprint> <Source> --format markdown
+drydock plan create <Blueprint> <Target>
+# Review and approve the draft plan in <Target>/QuarterDeck.
+drydock build status <Blueprint> <Target>
+```
+
+`init` creates the specification-independent Target baseline and QuarterDeck. `import` creates the
+Blueprint workspace and preserves the source material. `plan create`
+internally inventories the Blueprint inputs and writes the executable `BUILD_PLAN.md` into the
+Target. Configured Blueprint and Target roots belong in Drydock's user-scoped `.env`, never project
+`METADATA.md`.
+
+## Deferred Commands
+
+The following commands are registered and visible in help, but not yet
+implemented. Each returns a clear message and exits with code `2`:
+
+```bash
+drydock document generate <Blueprint> <Target>
+drydock document assemble <Blueprint> <Target>
+drydock document <Blueprint> <Target>
+drydock rigging update <Target>
+drydock rigging verify <Target>
+drydock build <Blueprint> <Target>
+drydock build score <Blueprint> <Target>
+drydock refit <Blueprint> <Target> <BOTH|BLUEPRINT|TGT> <Scope> <Change>
+drydock analyze <Blueprint> [<Target>]
+drydock import <Blueprint> <Source> --format <source|speckit>
+```
+
+## Configuration
+
+Drydock reads these global configuration values:
+
+| Variable | Purpose |
+|---|---|
+| `BLUEPRINT_DIRECTORY` | Root path containing all Drydock Blueprints |
+| `TARGET_DIRECTORY` | Root path containing all target software projects |
+| `LLM_PROVIDER` | Subscription CLI provider: `claude` (default) or `codex` |
+
+**Effective-value precedence:**
+1. Environment variables `BLUEPRINT_DIRECTORY`, `TARGET_DIRECTORY`, and `LLM_PROVIDER`.
+2. Values persisted in the user-scoped Drydock `.env` file.
+
+**Config file location** (OS-appropriate):
+- Linux/macOS: `~/.config/drydock/.env`
+- Windows: `%APPDATA%\drydock\.env`
+
+Set values with:
+
+```bash
+drydock config set blueprint_directory /path/to/blueprints
+drydock config set target_directory /path/to/projects
+```
+
+`SPECIFICATION_DIRECTORY` and `specification_directory` remain accepted as deprecated migration
+aliases for `BLUEPRINT_DIRECTORY` and `blueprint_directory`.
+
+## Source-Tree Launchers
+
+When developing, you can run Drydock without installing it:
+
+```bash
+# Bash (Linux/macOS)
+bin/drydock.sh --help
+
+# PowerShell (Windows)
+bin/drydock.ps1 --help
+
+# Python module
+python -m drydock --help
+```
+
+All three dispatch to the same CLI entry point as the installed `drydock` command.
+
+PowerShell structural behavior is defined but not runtime-verified in WSL environments.
+
+## LLM Execution Foundation
+
+Application functions pass a fully assembled prompt to the subscription-authenticated CLI runner:
+
+```python
+from drydock.llm import run_prompt
+
+result = run_prompt(
+    prompt,
+    target_directory,
+    llm="claude",                 # optional; LLM_PROVIDER or claude default
+    model="sonnet",               # optional
+    command_name="plan-create",
+    parameters={"blueprint": blueprint_name, "block": block_id},
+    debug=debug,
+    timeout_seconds=3600,
+    on_text=lambda chunk: print(chunk, end="", flush=True),
+    on_event=handle_structured_event,
+)
+```
+
+Every run writes timestamped prompt, human log, raw provider output, final output, and stderr files
+under `<Target>/logs/`. `<Target>/logs/executions.jsonl` contains one self-contained JSON object per
+run with the effective argv, working directory, caller parameters, artifact paths, hashes, status,
+and parsed provider statistics. The JSONL file is append-only and intentionally extensible for
+future provenance and staleness fields.
+
+Provider JSONL is read while the process runs. `on_text` receives Claude partial text deltas or
+Codex agent-message steps immediately; `on_event` receives structured Drydock lifecycle and
+provider events. The same events are appended immediately to `<Target>/logs/events.jsonl`.
+Timeouts terminate the child process and return exit code `124`; interruption terminates the child,
+records exit code `130`, and re-raises `KeyboardInterrupt`.
+
+Material Drydock product decisions and delivery milestones are separate from execution mechanics.
+Agents developing Drydock follow the Ship's Log Process in `AGENTS.md` and use the repository-local
+utility:
+
+```text
+python bin/ships_log.py record --event-type decision --title "..." --summary "..." \
+  --rationale "..." --source-type agent [--scope ...] [--evidence ...] [--tag ...]
+python bin/ships_log.py audit
+```
+
+The sole Ship's Log artifact is Drydock's `logs/ships_log.jsonl`. It is append-only, rendered by
+QuarterDeck's generic JSONL viewer, and intended as the direct input to downstream publishing
+tools. It is not a public `drydock` command or a target-project Rigging rule. No Markdown Ship's Log
+is generated.
+
+## Project Governance Documents
+
+- `docs/Drydock_Specification.md` — sole authoritative Drydock behavior specification; agents
+  require product-owner approval before changing it.
+- `docs/SOUNDINGS.md` — authoritative implementation acceptance/readiness checklist and completion
+  evidence.
+- `docs/SEA_TRIALS.md` — strategic product outcomes and proof-of-methodology criteria.
+- `AGENTS.md` — operating rules, development architecture, and the mandatory Drydock-only agent
+  decision-capture (Ship's Log) process.
+
+QuarterDeck exposes these documents and the other owned artifacts under `docs/` directly.
+
+`LLM_PROVIDER=claude|codex` may be set in the process environment or user-scoped Drydock `.env`;
+the process environment takes precedence and Claude is the default. API-key environment variables
+are removed before invoking either CLI.
+
+## Packaged Rigging Resources
+
+The installed wheel contains a synchronized copy of the Drydock Rigging at
+`drydock/resources/Rigging/`. This is the same tree as the root-level `Rigging/`
+directory; it is included so Blueprint import, validation, and Rigging commands work from an
+installed wheel without access to the source checkout. The installed wheel also contains the
+QuarterDeck runtime used by `drydock init <Target>`.
+
+When running from the source tree, Drydock uses the root-level `Rigging/` directly.
+When running from an installed wheel, it falls back to `importlib.resources`.
+
+## License
+
+Proprietary — Web Cloud Studio. See [LICENSE](LICENSE) for terms.
+No part of this software may be used without explicit written permission.