itc-world.com
ITC World – GlafyCo's infrastructure log
Quiet technical authority for the GlafyCo ecosystem — ITC World records real infrastructure choices, constraints, and trade-offs across E_MediaScience, AlbedoPulse, Clipositing, and related tools—as they happen, not as marketing. This site is for engineers, senior operators, and partners who need to understand how the system actually runs. No sign-up flows.
Non-negotiable Constraints
- ITC World — Quiet technical authority and infrastructure log only. No selling, no funnels, no product marketing. Documents real decisions; does not invent vendors or features.
- AlbedoPulse — Proprietary commerce-signal scoring engine for Clipositing and the wider E_MediaScience stack. Quantifies commerce-led virality and conversion velocity. Not a generic scraper or data cleaner.
- Clipositing — Live-selling-specific, commerce-signal-first clip compositing. Not a generic clipping tool.
- Brand — GlafyCo logo black/white only; no gradients or colour inside the logo. Green reserved for action and performance signals only.
- Realism — Locked progression planning across projects: capacity expands in defined stages as demand grows. High-level vendor references only; no operational secrets, credentials, or competitive topology published here.
E-MediaScience Stack Overview
The GlafyCo group is layered. ITC World sits underneath as documentation—not as a customer-facing product.
| Layer | Role | |-------|------| | GlafyCo | Parent engineering and IP hub; owns brands, domains, and architectural consistency | | E_MediaScience | Core PR intelligence SaaS — journalist discovery, scoring, outreach, campaign analytics | | AlbedoPulse | Underlying algorithmic scoring engine (“Powered by AlbedoPulse”) | | Clipositing | Specialised live-selling media tool layer; Production Engine bolt-on within EMS | | JournalistDirect | Free-entry journalist discovery surface (acquisition path into EMS) | | Ian Builds Agents | Public lab and distribution engine operated by GlafyCo — build narrative, not a consultancy homepage | | ITC World | Infrastructure and systems log for everything above |
Operational SaaS entities may handle customer contracts and billing; GlafyCo maintains IP, brand integrity, and long-term architecture.
What Gets Documented Here
Hosting and application platforms (high level)
- Web surfaces: Vercel for static and Next.js deployments where mapped in the domain plan
- Application and worker tiers: Railway or Render for API and background workloads as each product phase requires
- Data and auth: Supabase (PostgreSQL, Edge Functions, RLS) for E_MediaScience multi-tenant core
Decisions note why a vendor was chosen—cost discipline, deploy velocity, data residency fit—not step-by-step configuration.
Data and extraction infrastructure (high level)
- Octoparse MCP as the structured intelligence layer for journalist profile extraction in EMS
- Intent-based MCP calls return JSON payloads into scoring pipelines—no fragile HTML parsing in application code
- Pipeline TTL policies: hot → cold → delete; processing engine, not a long-lived data warehouse
Credentials, API keys, proxy pools, and account identifiers are never published on this site.
Vendor selection principles
- Prefer vendors that match current phase load—not aspirational enterprise scale on day one
- Document trade-offs honestly when a decision is reversed
- Marketing sites must not promise capacity the infra log cannot support
Why This Exists
ITC World keeps infrastructure decisions honest and grounded. It provides an audit trail for investors and technical partners, and ensures public marketing domains never over-promise beyond what the stack can deliver.
When a product ships a feature, the corresponding infra note should exist here—or the feature should not ship.