Nic Wanavit thanakijwanavit

Villa Price SDK v2 — Developer Quickstart

Standalone v2 client for the price database stack (dev-manual branch). V2 uses separate Lambda names, S3 buckets, DynamoDB table, and API paths from v1.

Install

Option A — PyPI (v1 SDK package; v2 module included when published):

pip install villaPricingSdk

Villa Pricing SDK v2 — Developer Guide

Package: villaPricingSdk
Version: 0.1.0
Install: pip install --upgrade villaPricingSdk==0.1.0

V2 stack (dev-manual)

VillaCoupon3 — Developer / PM Guide

For Aung. This explains how the VillaCoupon3 system is built, deployed, and operated.

Credentials (AWS keys + UAT login) are sent privately. This document has no secrets.

1. Purpose

VillaCoupon3 — UAT Test Guide

Hi Aung and Mickey — please help test the new coupon admin system.

Login credentials are sent separately (private channel). This document has no passwords.

1. Dashboards / URLs

Villa Market -- Delivery Distance Calculator

What it does

A serverless API that calculates delivery shipping cost from a customer's location to all nearby Villa Market branches. Send your lat/lng, get back eligible branches sorted by distance with delivery cost in THB.

Live API

POST https://km797c84si.execute-api.ap-southeast-1.amazonaws.com/Prod/shipping-cost

Villa Market Product Description Downloads

⚠️ Note: S3 signed URLs are signed with EC2 instance-role temporary credentials that rotate every ~6 hours. If a link returns 403, ping the engineer to refresh this gist.

Full Export (144.9 MB, 83,583 products)

Columns: cprcode, barcode, English name, Thai name, English description, Thai description, enhanced status, meta title (EN/TH), meta description (EN/TH), meta keywords, OG tags, schema JSON-LD

[Download villa_products_full.csv](https://villa-product-description-data.s3.ap-southeast-1.amazonaws.com/product-enhancement/data/exports/villa_products_full.csv?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=ASIA5J3DQBGOAQXP3RU2%2F20260407%2Fap-southeast-1%2Fs3%2Faws4_request&X-Amz-Date=20260407T015801Z&X-Amz-Expires=604800&X-Amz-SignedHeaders=host&X-Amz-Security-Token=IQoJb3JpZ2luX2VjEBIaDmFwLXNvdXRoZWFzdC0xIkYwRAIgXcAOE6A6WmTDCdPmbgmWGYLRpu5I9fRyE%2BOi00eJQbYCIHMZbrIljMygLexdHvEavgkv8S7wyr%2FLtsiPXtYLd7ByKtIFCNv%2F%2F%2F%2F%2F%2F%2F%2F%2F%2FwEQABoMOT

OpenClaw Multi-Agent Team Setup Guide

A complete guide to setting up a multi-agent AI team with OpenClaw, featuring specialized agents for different domains.

Overview

This setup creates a team of AI agents that can be accessed through a single Telegram interface. Each agent has a distinct personality and expertise.

Team Structure

OpenClaw Multi-Agent Team Setup Guide A complete guide to setting up a multi-agent AI team with OpenClaw, featuring specialized agents for different domains. ## Overview This setup creates a team of AI agents that can be accessed through a single Telegram interface. Each agent has a distinct personality and expertise. ## Team Structure | Agent | Role | Trigger | Purpose | |-------|------|---------|---------| | Wawa | Central Hub | (default) | Routes conversations, maintains context | | @milo | Strategy Lead | @milo | Strategic planning, OKRs, decisions | | @josh | Business Analyst | @josh | Metrics, pricing, competitive analysis | | @marketing | Marketing | @marketing | Content, trends, social monitoring | | @dev | Developer | @dev | Code, architecture, technical decisions | | @db | Database Guardian | @db | Beads/Dolt management | | @health | Health Expert | @health | Health, wellness, medical guidance | | @config | Config Expert | @config | Config validation, documentation

Deploying Gasclaw on Kubernetes (Helm)

Gasclaw runs a Gastown multi-agent workspace managed by OpenClaw on Telegram, with Kimi K2.5 as the LLM backend. This guide deploys it to any Kubernetes cluster using the included Helm chart.

Prerequisites

Kubernetes cluster (1.24+)
Helm 3
kubectl configured for your cluster
API keys: Kimi keys, Telegram bot token, Telegram owner ID

	Yes, but you must design the backup/recovery flow upfront. With DFNS delegated wallets, the user is the signer. Your company cannot just “reset” the wallet and move funds for them. That is the whole point of delegated/self-custodial signing. DFNS states that with delegated wallets, only the end user holds the credential required to sign transactions, and your organization cannot authorize transactions on their behalf.

	The simple answer

	You should support 3 backup layers:

	1. Synced passkey
	Apple iCloud Keychain / Google Password Manager / 1Password / etc.
	2. Multiple credentials
	Let the user add another passkey, phone, laptop, or hardware key.