Skip to content
CyclepediaThe trading encyclopedia
ITENESPT-BRFRDE

Assemblea

Assemblea, described as Assembly in English, combines a market-voting session with the Direktor video area. It shows sample consensus and reputation without turning a collective vote into a certain forecast.

On this page

Definition — Assemblea is the official product name; Assembly is its English descriptor. It combines a market-voting session with a Direktor video area. The session reveals the aggregate response distribution; previous-session consensus and reputation follow separate steps. These measures describe the participating sample, not a certain probability of the next move.

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.

In the historical codebase the product folder is named bias; in the interface and Cyclepedia its canonical product name is Assemblea, localised here as Assembly. The /assemblea/direkte and /assemblea/dirette aliases lead to the canonical /assemblea/direktor video area but do not define separate software products.

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.

Assemblea · session and Direktor Interactive path from an individual vote to consensus, reputation and Direktor video. Assemblea · session and Direktor Two surfaces in one software environment, with different data and limits Form a thesis before seeing the group; keep session, history and editorial content separate. 01 Two surfaces Session · Direktor They belong to one software environment 02 State and question window · market · horizon Read what the choices mean 03 Thesis and response thesis first · vote second A profile is required in the window 04 Reveal + consensus distribution · previous session They are separate events 05 Historical reputation many resolved sessions Do not judge it from one outcome 06 Direktor video episodes · player · access Availability depends on profile and episode Sample ≠ probability · reputation ≠ universal skill · video ≠ financial advice Cyclepedia diagram · Emiciclo
Session and Direktor share one environment, but sample, reputation and video content require distinct readings and limits.
Select the highlighted points to explore the detail

The two surfaces

Session and voting

The session presents structured questions about a market reading. An identified user records a response within the stated window; once the flow is complete or voting closes, the aggregate response distribution is revealed. Consensus on the previous session, where applicable, is a separate step; reputation updates over resolved sessions.

The main elements are:

  • the participant's chosen direction or scenario;
  • degree or intensity when the question includes it;
  • the aggregate distribution of current responses;
  • consensus on the previous session, when exposed;
  • reputation built from the history of resolved responses;
  • a leaderboard or comparison among participants, when exposed.

Direktor video

The Direktor area collects video episodes and lessons organised by format. The player may provide a timeline, moments or markers, captions and viewing telemetry; access to the latest episode or selected areas may depend on the current profile, while other content remains available under the app's rules.

The video is educational or editorial commentary. It must not be confused with session consensus and does not turn an analysis into a personalised recommendation.

Who it is for

  • Readers who want to compare their own view with a group's without erasing the original hypothesis.
  • Readers studying sentiment, collective behaviour and forecast quality.
  • Followers of Direktor content who want to find it in an organised environment.
  • Traders who want to observe the effect of their own confirmation bias over time.

It is not designed to produce a buy/sell signal or measure the whole market. People who do not vote, cannot see the session or leave the process are not represented in the observed sample in the same way.

Session tutorial

  1. Open Assembly and check the session state: open, closed, consensus or resolved.
  2. Read the full question before looking at consensus, if it is already visible. Identify the market, horizon and meaning of the choices.
  3. Form your own thesis. Record the scenario, reason and invalidation condition before voting.
  4. Sign in with your profile if you want to participate. Reading may be public, but voting requires identification.
  5. Record one considered response inside the stated window; do not interpret degree as leverage or position size.
  6. Wait for resolution. An open vote is not yet a completed historical measure.
  7. Compare your thesis with the revealed result. Keep the current distribution separate from any previous-session consensus and ask whether the group adds information or merely reassurance.
  8. Review reputation over many sessions. One positive or negative outcome does not estimate stable skill.

How to interpret consensus and reputation

Measure What it says What it does not say
Share of votes distribution of responses received objective probability of the future move
Consensus intensity how concentrated the sample is on one choice how large a position should be
Reputation history calculated under the product's rules universal competence across every market and horizon
Leaderboard ordering under the stated metric guarantee that the current leader will remain better in future

Three limitations are central:

  1. Self-selection. Participants choose to take part; the group is not a random sample of all traders.
  2. Regime dependence. Reputation accumulated in one context may not transfer to a different regime.
  3. Herding. Seeing a majority may encourage agreement without new evidence; see Herding.

Direktor area tutorial

  1. Open the video tab from Assembly navigation.
  2. Choose a format and an episode available to your profile.
  3. Check the title, date and scope before playback.
  4. Use the timeline, moments or captions, when present, to reach the relevant passage.
  5. Transcribe definitions and rules into a separate note; do not rely on memory of the video alone.
  6. Verify general concepts in Cyclepedia and keep the Emiciclo Method distinct from historical sources.

Data, access and privacy

  • The canonical route is /assemblea; the video area uses /assemblea/direktor with historical aliases.
  • General reading may be available without login; voting and personal functions require an account.
  • Responses, session state and reputation are persistent data linked to the profile under the product's rules.
  • Video visibility may vary by episode and access level. If the interface, pricing information and published conditions do not agree, do not infer an access entitlement yourself: check the current terms and ask support to confirm.
  • Playback telemetry describes use of the player; it does not prove understanding of, or agreement with, the analysis.

Read the current app notices before participating. Do not enter personal financial information in a vote when the interface does not request it.

Common problems

I cannot vote

Check that the session is open, the profile is authenticated and no response has already been recorded. A closed session may remain readable but cannot be modified.

Consensus does not appear

It may remain hidden until the expected phase or until the flow is complete or closed. Missing data is not neutral consensus.

Reputation does not change immediately

The measure updates when the session is resolved under current rules, not necessarily at the moment of voting.

A video is locked

Check login and profile level in the app. Availability may differ among the latest episode, previous episode and archive.

Relationship with the other software environments

  • Cyclepedia provides definitions and sources for assessing the theses discussed.
  • CycleSic and Cyclic Dashboard produce analytical readings separate from the vote.
  • Office lets users record whether consensus influenced a decision and recognise hindsight bias during review.
  • Tournaments measures results under a different rulebook: a competition ranking is not voting reputation.

Verified version

Editorial check: 8 August 2026. This guide documents the voting/consensus/reputation session and the Direktor video area. Session times, scoring formulas, editorial schedule and access to individual episodes are variable configuration; consult the current interface.

Sources

  • Assembly — official app surface, checked on 2026-08-08.
  • Direktor — official video area linked to Assembly.
  • Current application code and rules for sessions, voting, reputation and the player — proprietary primary sources checked during review; they do not constitute independent verification.
Suggest an edit My proposals