Skip to content

Ufficio

Ufficio, described as Office in English, is Emiciclo's trading journal: it imports compatible account data and organises dashboards, analytics, trade details and review with disclosed synchronisation limits.

Ufficio is the official product name; Office and Direktor Office are its English descriptors, and its extended name is Ufficio d'er Direktor. It is the trading journal and analytics environment in the Emiciclo ecosystem. It imports available data from compatible accounts, organises trades and results, and offers review tools. It automates the accounting side of a journal, but it cannot know a trader's motives, emotions or decision quality by itself.

Transparency note — Emiciclo publishes Cyclepedia and produces the software described here. This page combines official documentation with a user guide: it is not an independent review or financial advice. Features, access and conditions were checked on the stated date; limitations receive the same prominence as capabilities.

How to read the diagram — Select one of the six stages, or use Tab and the arrow keys. The explorer shows the verified detail and a link to the relevant section.

Ufficio · from data to review Interactive path from a read-only connection to trading-process review. Ufficio · from data to review Connect, synchronise, reconcile and turn history into a process Automation imports accounting facts; motives and emotions remain annotations. 01 Data connection provider · API · read-only No trading or withdrawal permissions 02 Synchronisation status · delay · manual sync Saving is not importing 03 Reconciliation side · size · fees · time Compare a sample with the source 04 Dashboard + detail P&L · equity · recent trades The context chart is reconstructed 05 Analytics filters · drawdown · export Sample and capital change the reading 06 Journal and review setup · notes · voice · reminders Process quality is annotated Read-only ≠ complete history · missing ≠ zero · never enable trading or withdrawals Cyclepedia diagram · Emiciclo
Imported data becomes useful only after synchronisation, reconciliation and a conscious review of the process.
Select the highlighted points to explore the detail

Who it is for and prerequisites

Office is for traders who want to turn transaction history into a repeatable verification process:

  • beginners can avoid reconstructing prices, size and results from memory;
  • regular traders can filter periods and instruments, annotate setups and monitor drawdown;
  • traders who already keep a journal can compare automatic data with qualitative observations without confusing the two.

Connecting an account requires an Emiciclo profile, a currently supported provider and API credentials configured as read-only in the wizard. Do not enable trading or withdrawal permissions. If you do not want to connect external data, first inspect any demonstration modes available in the current interface.

A conceptual prerequisite is understanding that profit, execution quality and plan adherence are different objects. The journal measures what it receives and what you record; it cannot reconstruct intentions that were never entered.


What it does and does not do

Office lets you:

  • import transactions made available through active integrations;
  • inspect dashboards with P&L, equity development, summaries and filters;
  • analyse performance by period, market or pair and observe drawdown;
  • open a trade detail and reconstruct the available chart context;
  • export data when the feature is exposed;
  • set starting capital and preferences required for calculations;
  • add setups, text notes, voice notes and reminders to the journal;
  • run a manual synchronisation from Analytics alongside scheduled processes;
  • use Help and the guided tour to explore the environment with demonstration data.

Office does not:

  • act as a broker or a place to custody funds;
  • require trading or withdrawal API permissions for its normal read-only workflow;
  • guarantee that every provider exposes the same historical depth;
  • infer an entry reason, emotional state, process error or planned risk automatically;
  • make different strategies comparable without adjusting for capital, exposure, costs and duration;
  • turn a scorecard or rising equity curve into evidence of future skill;
  • provide financial advice.

Interface map

Area Purpose Recommended check
Dashboard summary, P&L, equity, aggregate indicators and recent trades period, filters and synchronisation state
Trade detail transaction data and entry/exit chart context symbol, side, size, fees and timestamp
Analytics / Studio performance, drawdown, comparisons, scores and export starting capital and sample consistency
Journal setups, notes, voice and reminders what is automatic versus what you entered
Settings profile, preferences and available integrations key permissions and correct provider
Help / tour workflow explanation and demonstration dataset always distinguish demo data from real data
Emiciclo profile shared session, language and access active account and login origin

The former “Sacred Hour” item still present in some Office routes is a legacy/work-in-progress surface. It must not be confused with Holy Hour, which is now one of the two zones within Tournaments.


Essential tutorial, step by step

  1. Sign in to the Emiciclo profile and open Office. If you only want to learn the layout, start Help or the tour before connecting real data.
  2. Define the journal's purpose. Choose one concrete question, such as “Am I following my plan?” or “Which setup creates the largest drawdown?”.
  3. Check the provider in the current wizard. Availability can change; do not rely on an old list found in a page or screenshot.
  4. Create read-only API credentials. Disable trading and withdrawals, keep the secret out of notes and chats, and check any passphrase or restriction required by the provider.
  5. Complete the required account checks. Follow the UID, account-type or other steps shown by the wizard without assuming that every integration is identical.
  6. Wait for the first synchronisation. Saving a key does not mean that the full history appears immediately. If needed, use manual synchronisation in Analytics.
  7. Validate a small sample. Compare at least a few trades with the original history: side, quantity, entry, exit, fees and time.
  8. Set the reference capital correctly. Equity, percentages and drawdown can mislead when the base does not represent the analysed account.
  9. Open the detail for a closed trade. Check the reconstructed chart and record the reason, plan, execution and any error. The automatic chart cannot contain indicators or drawings that were absent from the imported data.
  10. Review, do not merely account. Complete notes at the end of the day; each week, compare patterns, plan adherence and risk, not only P&L.

How to read the outputs

Output What it describes What can distort it
P&L result attributed to imported trades inside the selected scope missing trades, fees, funding, conversions and filters
Equity development calculated from the configured base incorrect starting capital, unrepresented deposits or withdrawals
Drawdown loss from the previous peak within the sample short history, missing data and capital changes
Win rate share of trades classified as positive average payoff, break-even trades and fill aggregation
Score / DNA proprietary summary of several measures formula, sample and correlation among metrics
Trade chart reconstructed context around entry and exit symbol mapping, candle availability and timeframe
Setups and notes qualitative classification entered by the user inconsistent categories and retrospective memory

A metric becomes useful only when you know which rows it includes. Before comparing periods, keep filters, capital and units consistent. Before comparing traders, consider leverage, exposure, risk and the distribution of results.

Common error — Treating imported P&L as a complete journal. Prices and fees may be automatic; motive, emotion, invalidation and plan adherence still require deliberate recording.


Data, access and privacy

  • Integrations and historical depth depend on the provider, account and available endpoints. This guide does not publish a fixed exchange list because the operational catalogue may change.
  • Use read-only credentials exclusively. If the provider's interface does not let you disable trading and withdrawals, stop the connection and ask for support.
  • Synchronisation may be scheduled or manual and is not necessarily immediate. Missing data must be marked as missing, not interpreted as zero.
  • Providers may impose pagination, historical windows, rate limits, expiry or passphrases. Always keep the original history for reconciliation.
  • Office processes profile and transaction data required for the requested functions. Never enter API secrets in journal notes, screenshots, public tickets or conversations.
  • For purposes, retention and rights, read the official privacy notice.

Troubleshooting

The key is rejected

Check the provider, account type, read-only permissions, any passphrase, IP restrictions, expiry and copied whitespace. Do not broaden permissions “just to test”.

Trades do not appear

Wait for the synchronisation cycle, then use manual sync in Analytics. Check the date range, filters, account or sub-account and historical depth supplied by the provider. If the source does not return complete history, document the scope before reading the metrics.

P&L or equity does not match the provider

Compare starting capital, timezone, fees, funding, currency conversion, partial fills and movements not classified as trades. Begin with one transaction, not the aggregate total.

The trade-detail chart is empty

Check the symbol and timestamp. The candle provider may use a different ticker from the transaction source; report the mapping instead of manually substituting a non-equivalent market.

The session or a page does not refresh

Reload once, check the profile state and re-enter through the app. If the issue persists, retain the time, route and error message, making sure support screenshots do not expose keys or personal data.


Relationships in the ecosystem

  • CycleSic can add chart context to connected positions in enabled workflows; Office remains the place for structured review.
  • Tournaments uses linked account and verification flows, but rankings and rules do not replace a personal journal.
  • Cyclepedia provides the method for reading journaling, drawdown and process quality.
  • Emiciclo Method may propose workflows; Office records data and observations without certifying that the method was applied correctly.

Version check

This guide was checked on 2026-08-08 against the routes, dashboard, Analytics, journal, Help, Learn Tour, integration catalogue and synchronisation flows in the Emiciclo runtime. Journal and review capabilities were confirmed; no provider list, price or promise of historical depth was frozen into the page.

To verify a later change, check in order: the provider shown by the wizard, requested permissions, last-sync date, active filters and a sample reconciled with the source. If the UI differs from this guide, use the UI for the operation and report the editorial section that Cyclepedia should update.


Sources

  • Office in the Emiciclo app — current interface, onboarding and operational state.
  • Official Emiciclo website — ecosystem identity and access to public services.
  • Official access and plans — current source for access conditions, not reproduced in this guide.
  • Emiciclo privacy notice — data processing and controller contact details.
  • Cyclepedia technical check: editorial comparison on 2026-08-08 with src/products/ufficio/, authentication and profile contexts, the exchange catalogue, synchronisation functions and tutorials in the runtime repository.

Operational access

Open Office in the official app — neutral external link. Before connecting data, verify the provider, read-only permissions, privacy and limitations shown by the current wizard.