Convert Wiki Pages to a Tessl Tile

Problem/Feature Description

A platform engineering team has a collection of internal wiki pages that they want to convert into a Tessl tile so their AI assistant can help with day-to-day platform tasks. The content is currently in markdown files but isn't structured for AI consumption.

Your job is to restructure these files into a proper Tessl tile at ./platform-tile/ with workspace "platform-eng" and name "platform-eng/platform-ops". Version it as 0.1.0 with summary "Platform engineering operations and reference".

Input Files

The following files are provided as inputs. Extract them before beginning.

=============== FILE: inputs/wiki/database-setup-guide.md ===============

Database Setup Guide

This document explains how to set up a new PostgreSQL database for our services.

Step 1: Create the Database

Run the following command to create a new database:

createdb -h db.internal.acme.com -U admin service_db

Step 2: Apply the Base Schema

Apply our standard schema template:

psql -h db.internal.acme.com -U admin -d service_db -f schema/base.sql

Step 3: Configure Connection Pooling

Set up PgBouncer with our standard config:

cp /etc/pgbouncer/template.ini /etc/pgbouncer/service_db.ini
# Edit the file to set:
# pool_mode = transaction
# max_client_conn = 200
# default_pool_size = 25

Step 4: Register in Service Discovery

Add the database to Consul:

consul kv put services/service_db/db_host db.internal.acme.com
consul kv put services/service_db/db_port 5432

Step 5: Verify Connectivity

psql -h db.internal.acme.com -U admin -d service_db -c "SELECT 1"

=============== FILE: inputs/wiki/service-catalog.md ===============

Service Catalog

Authentication Service

• Port: 8080
• Repository: github.com/acme/auth-service
• Database: auth_db
• Dependencies: Redis, PostgreSQL
• Health Check: GET /health
• Owner: Identity Team

Payment Service

• Port: 8081
• Repository: github.com/acme/payment-service
• Database: payments_db
• Dependencies: PostgreSQL, Stripe API
• Health Check: GET /api/health
• Owner: Payments Team

Notification Service

• Port: 8082
• Repository: github.com/acme/notification-service
• Database: notifications_db
• Dependencies: PostgreSQL, SendGrid, Redis
• Health Check: GET /healthz
• Owner: Comms Team

API Gateway

• Port: 443
• Repository: github.com/acme/api-gateway
• Dependencies: Auth Service, all backend services
• Health Check: GET /status
• Owner: Platform Team

=============== FILE: inputs/wiki/coding-standards.md ===============

Team Coding Standards

These are general guidelines for our codebase. We use them loosely and they are more like suggestions.

Naming

• Use camelCase for variables and functions
• Use PascalCase for classes and interfaces
• Use UPPER_SNAKE_CASE for constants

Error Handling

• Always use try/catch for async operations
• Log errors with structured logging (use our logger, not console.log)

Testing

• Write unit tests for business logic
• Use integration tests for database operations
• Aim for 80% coverage on new code

Code Review

• All PRs need at least one approval
• Use conventional commits for commit messages

Output Specification

Produce the complete tile directory at ./platform-tile/ with:

1. tile.json — valid manifest
2. All content files properly categorized and structured
3. A file called conversion-log.md in the working directory documenting:
   • How you classified each source file and why
   • What structural changes you made
   • The approach you took for the conversion