Company Register

Обновлено: 2026-07-03 Owner: Founder / You Статус: v0.1, без секретов

Назначение

Company Register фиксирует операционную структуру Design Corporation без хранения секретов, токенов, паролей, полных банковских реквизитов или приватных payout details.

Документ нужен для быстрых ответов на вопросы:

1. Чем владеет компания.
2. Какие аккаунты относятся к компании, а какие к личным потокам.
3. Где не хватает данных для бухгалтерии, налогов и управления рисками.
4. Какие изменения требуют отдельного owner approval.

Правило безопасности

В этом документе разрешено хранить:

• публичные юридические данные;
• назначение аккаунтов;
• владельца контура;
• статус данных;
• ссылки на канонические документы и runtime paths без секретных значений.

Запрещено хранить:

• пароли, токены, refresh tokens, private keys;
• полные банковские реквизиты, card numbers, seed phrases;
• raw payout documents, если они содержат private identifiers;
• налоговые кабинеты с login/password;
• персональные документы owner-а.

Юридическое ядро

Поле	Значение	Статус	Источник
Legal name	Design Corporation Sp. z o.o.	confirmed	Company Profile
Jurisdiction	Poland	confirmed	Company Profile
Launch year	2016	confirmed	Company Profile
NIP	8971829745	confirmed	Company Profile
Public group brand	Group Design Corporation	confirmed	Company Profile
Main public email	info@designcorp.eu	confirmed	Company Profile
Main public phone	+48 515 582 273	confirmed	Company Profile
VAT status	unknown in docs	needs verification	accounting source required
Accountant / księgowość contact	unknown	needs owner input	not stored yet
Registered address	not stored in docs	needs policy decision	public registry / invoice docs

Account Register

Account / identity	Type	Purpose	Owner	Status	Rule
info@designcorp.eu	company email / integration identity	Company communication, integrations, future company-owned publishing, partner/SaaS contexts	Founder / You	active	Corporate default; do not use for private payout flows unless explicitly decided
design.corp.ua@gmail.com	personal Amazon/KDP/payout identity	Current personal KDP books, reports and payouts	Founder / You	active	Keep separate from company ownership without migration plan
GitHub DesignCorporation	company engineering org/user	Repositories, projects, CI/CD, source control	Founder / You	active	No secrets in repos; production deploy approval remains separate
Production server admin user	infrastructure identity	Runtime operations on DesignCorp host	Founder / You / Agent Platform	active	Document only paths and services, never credentials
Telegram owner/admin identity	operations identity	Agent control plane and operational approvals	Founder / You	partial	Keep allowlists in runtime env/state, not docs
Amazon Ads partner/API context	integration account	Ads API / reporting / partner access	info@designcorp.eu context	partial	Live Ads writes require explicit approval and audit trail
KDP publisher account for current personal books	personal publishing account	Existing personal books and payouts	design.corp.ua@gmail.com context	partial	Separate from future company-owned publishing

Finance / Banking Register

Area	What to record	Current status	Storage rule	Next action
Company bank accounts	Bank name, currency, purpose, statement export cadence	unknown	Do not store full IBAN/card data in docs	Add bank names and currencies only in Finance Ledger
Payment processors	Stripe/PayPal/other, settlement currency, fee model	unknown	Store account purpose, not keys	Inventory Print/Hub payment flow in Finance Ledger
Invoicing system	Tool, invoice numbering, VAT rules, accountant handoff	unknown	Store process, not private customer docs	Define current invoice process in Finance Ledger
Tax filings	VAT/PIT/CIT filing cadence and owner	unknown	Store cadence and owner only	Confirm with accountant
Subscriptions	Tool, monthly cost, owner, card/source	unknown	Do not store card details	Build subscription ledger
Amazon/KDP payouts	Marketplace, currency, payout account type	partial	No raw payout identifiers	Separate personal vs company-owned economics

Asset Register

Asset class	Current source	Status	Next action
Domains	Topology	partial	Ensure all active/legacy domains are classified
Repositories	Projects Portfolio, Agent Contracts	partial	Add status and revenue role per repo
Runtime services	Topology, runbooks	partial	Map each service to owner and criticality
Brand assets	design docs and project repos	partial	Identify canonical logo/font/color sources
Books / publishing assets	Book / LibraryBookDesignCorp project docs	partial	Separate personal works, company assets and client/SaaS data
Client data	project-specific apps	unknown	Define retention and access policy
Financial documents	accounting exports / invoices	unknown	Define storage outside docs

Ownership Boundaries

Boundary	Current rule	Risk if violated
Personal KDP vs company publishing	Current personal books stay under personal KDP/payout identity unless migration is explicitly planned	Tax/accounting confusion, duplicate ownership, payout mismatch
Company integration vs customer/client data	Company integration accounts may process connected account data but do not own client assets by default	Incorrect revenue attribution and compliance issues
Production deploy vs git push	Git push is not production deploy; production rollout requires approval and runbook	Accidental live change or rollback gap
Docs vs secrets	Docs store process and ownership, not secret values	Credential exposure
Revenue hypothesis vs accounting fact	Revenue docs may track strategy, but profit answers require source, period and formula	Wrong cash/profit decisions

Approval Matrix

Change type	Approval required	Notes
Add/update public company info	Founder / You	Keep synced with legal pages
Change payout account	Founder / You, plus accounting review	Requires audit trail and migration plan
Change tax/VAT profile	Founder / You, accountant	Never infer from app settings only
Connect new third-party financial tool	Founder / You	Document purpose and data access scope
Rotate or create credentials	Founder / You / Agent Platform	Store only in approved secret location
Git push for ordinary docs/code changes	Owner approval policy for current repo	Production deploy remains separate
Production deploy	Founder / You	Follow runbook and smoke checks
Ads write operation	Explicit owner approval	Capture before/after and reason

Missing Data Queue

Priority	Missing data	Why it matters	Target document
P0	Company bank account list by currency and purpose	Needed for cashflow and payout routing	Finance Ledger
P0	Current accountant/contact and filing cadence	Needed for tax deadlines and compliance	Company Register
P0	Subscription/tool expense list	Needed to know monthly burn	Finance Ledger
P0	Payment processor setup for Print/Hub	Needed to calculate real margin	Finance Ledger
P1	Domain renewal owner and expiry tracking	Avoid service loss	Topology / Risk Register
P1	Client data retention policy	Compliance and operational safety	Risk Register
P1	Brand asset source of truth	Consistent public surfaces	Design docs

Next Actions

1. Add non-sensitive bank/accounting metadata to Finance Ledger: bank names, currencies, purpose, statement cadence.
2. Fill Finance Ledger for current month with income, expenses, VAT/fees and cash-after-deductions model.
3. Classify every project as revenue, internal, paused, legacy or unknown.
4. Maintain Risk Register for account mixing, secrets, backups, domain expiry and tax deadlines.
5. Add Decision Log for ownership and payout decisions.