DevOps Team Tile Creation

Problem/Feature Description

A DevOps team at a mid-sized company has been using an internal wiki to document their processes, but they want to make their knowledge available to AI coding assistants through Tessl. They have three pieces of content they want to package:

1. Incident Response Runbook — A step-by-step procedure describing how to respond to production outages, including triage, escalation, mitigation, and post-mortem steps.
2. Infrastructure Architecture — A reference document listing all services, their endpoints, ports, and dependencies. Purely factual.
3. Deployment Freeze Policy — A short policy stating that all deployments MUST be frozen during the holiday season (Dec 20 – Jan 5) and NEVER deployed on Fridays after 4pm.

The team's workspace is called "acme-devops" and they want the tile named "acme-devops/ops-knowledge". The tile version should be 1.0.0 with a summary "DevOps operations knowledge for the infrastructure team". It should be a private tile.

Output Specification

Produce the following:

1. A complete tile directory at ./ops-knowledge/ containing:

   • A valid tile.json manifest
   • All necessary content files with appropriate content and structure
   • Proper directory organization

2. A file called plan.md in the working directory explaining:

   • How you classified each piece of content (and why)
   • The directory layout you chose
   • The shell command(s) you would use to scaffold this tile via the tessl CLI (with all required flags)
   • The shell command to validate the tile after creation

Include realistic but brief content in each file (a few sections each — don't write full runbooks).