3.1 KiB
Global Agent Instructions for Workspace
Storage Rules & Departmental Isolation (MANDATORY)
1. Dedicated Project Root Folders
All projects must strictly reside in their dedicated workspace root directories. No project data, scripts, or files may be created directly in /workspace/:
- Ekeepa:
/workspace/ekeepa/<department>/ - Cafe Bazaar:
/workspace/bazaar/<department>/ - Divar Hardware:
/workspace/divar/<department>/ - Davvvat Events:
/workspace/davvvat/<department>/ - Global E-Commerce:
/workspace/ecommerce/<department>/(TMall, LazMall, DKMall, E-Commerce) - Trading System & Journals:
/workspace/trading/<department>/(Daemons, Evaluators, MT5, Backtests, Journals) - Mindroo & Verification:
/workspace/mindroo/<department>/(Phone Verification, Datasets, KYC, Operations) - Turkey Migration & Uni:
/workspace/tr_migration/<department>/(Istanbul Portals, Scrapers, Multi-lang Resumes) - London Infra & Architecture:
/workspace/london_infra/<department>/(Blueprints, Handoffs, Compose, Traefik, Authelia) - Crawling Tools & Captcha:
/workspace/crawling_tools/<department>/(Watercrawl, Captcha Debug, Screenshots) - Kavosh Social Verification Gateway:
/workspace/kavosh/(Kavosh API, BoxAPI, HikerAPI, Dashboards, Master Reference)
2. Departmental Mapping
Inside each project root, all artifacts must follow the 5 London departments:
executive/: Strategic memos, investor decks, executive summaries, briefs, blueprints.engineering/: Repositories, crawlers, daemons, backend/frontend source, databases, build scripts.growth/: Dashboards, marketing campaigns, SEO, media assets, benchmarks, templates.operations/: CRM, telegram bots, task scheduler configs, live journals, logs, telemetry, screenshots.finance/: Ledgers, budget sheets, P&L models, backtest empirical data, compensation, unit economics.
3. Policy Adherence
Consult each project's ORGANIZATION_POLICY.md before generating files. Never place loose files in /workspace/.
4. Zero Symlinks Rule (CRITICAL & MANDATORY)
- STRICT BAN ON ROOT SYMLINKS: Creating shortcuts / symbolic links (symlinks) in
/workspace/root is STRICTLY FORBIDDEN across all profiles and all agents under any circumstance unless explicitly requested by the user. - NO BACKWARD COMPATIBILITY SHORTCUTS: Never create symlinks for backward compatibility or ease of access in
/workspace/. All tools, scripts, and commands must use absolute or relative paths pointing directly to/workspace/<project>/<department>/. - IMMEDIATE ENFORCEMENT: Any attempt to
ln -soros.symlinktargeting the/workspace/root directory is a direct policy violation.
Kavosh API & Social Verification Mandatory Instruction (CRITICAL SSOT)
Whenever asked about Kavosh API, social verification, BoxAPI, HikerAPI, pricing, missions, or dashboards (kavosh.zebellkhan.com/*), ALL AGENTS MUST FIRST READ /workspace/kavosh/KAVOSH_MASTER_REFERENCE.md completely. This document is the single authoritative source of truth. All files, dashboards, documentation, and test data for Kavosh API must strictly reside in /workspace/kavosh/ and be updated only there.