Install The Partenon in 90 Minutes
A live, hands-on session every 15 days. You will leave with Partenon running on your machine and your first three heroes configured for your business.
Installations Goal
Revenue Organized
Stripe Payments Processed
Security Audits Run
Leave With a Working System
The workshop is not a demo. You install, configure, and run Partenon on your own machine or server.
A Working Local Install
Partenon runs from ./install.sh. The base system works without live credentials. You get a local dashboard, the Scribe demo, and a clear .env file ready for your keys.
Three Heroes Configured
Choose Scribe, Strategist, and one domain hero based on your operation. We load your documents and set the first missions.
A Clear Live / Connect / Roadmap Map
You will know exactly what works today, what needs your API keys or accounts, and what is still being built. No surprises after the session.
Choose Your Install
Two supported paths. Both use the same public repository and the same installer.
Prerequisites
- check Python 3.10 or newer
- check Node.js 20 or newer
- check npm
- check Git
What happens
- arrow_forward Creates
.venv - arrow_forward Copies
.env.example - arrow_forward Runs Scribe demo
- arrow_forward Hermes CLI is optional
git clone https://github.com/cuentadeservicio377-cell/partenon.git cd partenon ./install.sh
No live credentials required. The dashboard opens on http://localhost:3000.
Prerequisites
- check Ubuntu 22.04 or newer
- check Docker & Docker Compose
- check SSH access
- check Firewall access to ports 3000 and 8000
What happens
- arrow_forward Builds API, dashboard, and Postgres
- arrow_forward Exposes dashboard on port 3000
- arrow_forward Exposes API on port 8000
- arrow_forward Add a reverse proxy for production
git clone https://github.com/cuentadeservicio377-cell/partenon.git cd partenon docker compose up --build -d
Use a reverse proxy with TLS for any shared or production deployment.
What We Do in 90 Minutes
Four focused blocks. Each one moves from installation to real business use.
Clone, Install, and Run the Demo
Clone the repo, run ./install.sh, and confirm the Scribe demo output. We fix environment issues live.
Load Documents Into Your First Three Heroes
Pick Scribe, Strategist, and one domain hero. We load your files, run the first tools, and label what is live versus what needs credentials.
Build Your First Automation
Set optional credentials and run a routing command. See how a plain-language request maps to the right hero and what the output looks like.
Weekly Reviews and CRONs
Configure the Brain to run a weekly review, track objectives, and generate a morning briefing. We set realistic CRONs you can refine later.
Bring Your Business Context
The more context you bring, the more we configure during the session. If you do not have a document ready, use the prompt with any AI assistant to extract it.
No documents? Use an AI assistant first.
Paste the prompt for each hero into Kimi Code, ChatGPT, Claude, or any assistant you already use. Answer its questions. Save the output and bring it to the workshop.
Bring bank statements, expense receipts, income spreadsheets, and a supplier list. The Scribe turns them into a .finance dashboard.
- Last 3 months of bank statements
- Receipts or invoices for fixed and variable expenses
- Income source list
- Supplier or vendor names
Ask me questions one at a time about my business finances. Then output a structured list with: income sources, fixed expenses, variable expenses, suppliers, and any financial documents I should gather for my bookkeeper.
Bring a short brand description, logo files, social handles, and any existing posts or ads. The Herald writes a .design file.
- One-paragraph description of what you sell
- Logo files or brand colors
- Social media handles
- Recent posts, ads, or emails you liked
Ask me questions one at a time about my brand. Then write a concise .design file with: brand voice, target audiences, key messages, visual notes, and a 4-week content starter plan.
Bring a Stripe account in test mode, a product or service list, and prices. The Collector creates payment links and invoices.
- Stripe account (test mode is enough)
- Product or service names
- Prices and currencies
- Common invoice terms
Ask me questions one at a time about what I sell. Then output a structured list with: products or services, prices, currencies, and the payment terms I should set up in Stripe.
Bring a list of services and API keys you use and who has access to them. The Guardian audits key strength and access.
- Services with API keys (OpenAI, Stripe, Google, etc.)
- Who has admin access to each service
- Shared passwords or vaults you currently use
Ask me questions one at a time about the services and accounts my business uses. Then output a security inventory with: service name, purpose, who has access, and what type of credential it uses.
Bring your current project list, calendar tool, and top three priorities. The Strategist builds projects and checklists.
- Open projects or initiatives
- Calendar tool you use
- Top 3 priorities for the next 30 days
- Recurring meetings or deadlines
Ask me questions one at a time about how my business operates. Then output a project list with: project name, deadline, owner, and the first three tasks for each.
Bring a client or vendor list and any messages you need to follow up on. The Diplomat maps relationships and drafts follow-ups.
- Client and vendor names
- Status of each relationship
- Recent emails or messages pending reply
- Key dates or promises made
Ask me questions one at a time about my clients and vendors. Then output a relationship map with: name, status, last contact, next follow-up, and any pending promise.
Bring previous decisions, notes, or company objectives. The Brain stores memory and detects conflicts across heroes.
- Company objectives or annual goals
- Important decisions made in the last quarter
- Notes from recurring meetings
Ask me questions one at a time about what my business has decided and where it is headed. Then output a memory summary with: objectives, key decisions, open questions, and any contradictions I should resolve.
Automations That Run After the Session
During the workshop we configure the Brain to keep the system moving between sessions. Full autonomy grows as you connect more integrations.
Weekly Review
Every Sunday at 20:00 the Brain scans active projects, objectives, and follow-ups, then flags what needs attention.
Morning Briefing
A short daily summary with today's priorities, pending follow-ups, and any deadline approaching in the next 48 hours.
Objective Nudges
When an objective deadline is near, the Brain reminds the assigned owner and suggests the next concrete action.
The Brain uses SQLite by default and can scale to Postgres for team memory. We configure the first CRONs in the workshop; you refine them as your operation grows.
Built for Your Organization
We adapt the install session for the audience, the tools, and the pace of your group.
Coworking Spaces
Group installs for members
Universities
Curriculum-aligned sessions
Professional Associations
Industry-specific examples
Networking Groups
Founder cohorts
Enterprise Teams
Private VPC deployments
Workshop 2.0
One month after the first session, we open a follow-up workshop. We review what is not working, fix integrations, add more heroes, and tune your automations. Attendees from the first session get the link automatically.
JOIN THE WAITLIST arrow_forward