An academic platform where students’ questions become real collaborative projects. The funnel is the product — and it cannot be skipped.
The good answer was given three months ago. Nobody finds it again. Every academic year starts over on the same questions.
A board, a shared folder — cut off from the discussion that produced them. Six months later nobody knows why that task existed.
The project ends, the report is handed in, the file stays with one person. Whoever meets the same problem next year will never know it was solved.
LECO closes the loop: the question, the discussion, the structured work, the result — and the result that becomes a public resource again.
This is the only place on this page where you see the product.
A post tied to one to five topics and to one or more courses. You cannot publish without saying what it is about. The asker marks a single best answer — a switch, not a vote count.
Zero pivot at (2,2). Is partial pivoting enough, or is another method needed?
Partial pivoting is enough here. The matrix is invertible — the failure comes from row order, not conditioning.
A. NdioneSame case in lab 4. The counter-example is in the resource linked to the project.
M. TraoréEdited twice — public history, not deletable
The public Q&A stays public. The group keeps its internal conversations, attached to the project or to a work item. A message can be edited for fifteen minutes, and only while the discussion is unresolved.
Do we keep both methods in the atlas, or only the one from the course?
Both. The second explains why the first one fails.
Two methods, one notation. To carry into the output.
Six item types, four states, three views on the same data. The blocked state cannot be declared: it is computed from whatever blocks it.
ID98B-5 is blocked by ID98B-3 — the state is computed, never typed in
Draft, in review, approved, published. A public artefact never skips review. Once published it becomes a resource the next ones will find.
Once published, the output returns to the public Q&A as a reusable resource
This is not an interface suggestion. It is the shape of the product.
A public post tied to one to five mandatory topics and to one or more courses.
It declares a goal, an expected result, and the open roles with how many people each one needs.
It is not a like, it is not a follow: it is a declared commitment to do one thing.
When the conditions are met, the proposal becomes a private workspace for the committed group.
Report, paper draft, comparison table, dataset, prototype, bibliography, synthesis, presentation, open resource.
If someone withdraws, the condition breaks and the proposal steps back down. You cannot fake being ready.
“This funnel exists to avoid empty projects. Users cannot create a complete project with one click.”
The create menu has two entries. There is no “create project” button — the column tying a project to its proposal is mandatory, and no endpoint creates a project.
Six item types, an enforced hierarchy, and three views on the same data.
Editable inline. Item numbers are never reused, not even after a deletion.
Columns by state, draggable cards — four states, with explicit reopening from done.
Bars and dependency curves: ID98B-5 starts after ID98B-3, because it depends on it.
Task and bug under a story or an epic. Feature and story under an epic only. Subtask requires a parent, an epic has none. An item with children can no longer change type.
Two links: blocks and relates to. The blocked state follows from them. The graph detects cycles on every change and refuses the one that would create one.
32 permissions across seven areas compose reusable role templates. Asking to transition an item automatically adds reading it and reaching the workspace — an incoherent role cannot be built.
A public question, an internal discussion, a decision note, a work item — readable together, never in four tools.
The group asks the rest of the platform, choosing how much context to show: the project link, the topic only, or nothing.
Attached to the project or to a work item. Never to anything else. Resolvable, and a message stays editable for fifteen minutes.
An answer from the public Q&A can become a project resource. The platform’s knowledge enters the work.
The public Q&A, flat: one question, one to N answers.
The group’s internal conversations, resolvable.
Items, their states, their dependencies.
Status posts on the project timeline, public or internal, with approval.
The deliverables and their review.
Links, files, notes — or an answer reused by the project.
This is where work becomes knowledge again.
The state turns to done. Reopening stays possible, explicitly.
A decision note, short, attached to the work it explains.
Followers receive output broadcasts.
Reviewed, published, findable — the resource for whoever comes next.
First name, last name, bio, university, department, academic level. No anonymous mode, ever.
Ask the question from the course, and watch it become shared work.
Open a lead, declare the missing roles, gather the group.
See what the cohort is looking for, and what it produces.
Structure collective work without leaving the discussion that started it.
Move from a review thread to a reviewed, published deliverable.
Turn a cohort into projects that leave a reusable trace.
“The asker knows their question better than random voters.” Instead, a switch: one best answer, chosen by the author.
“Flat Q&A: a question has one to N answers, full stop.” Answers can answer each other. There is no comment entity.
“LECO is an educational community with real identity.” The profile is a privacy-respecting portfolio of contributions.
Passkey or magic link by email. Nothing else to remember, nothing else to lose.
Opening the link does not consume the token: an explicit confirmation is required. It is a defence against mailbox security scanners, which would burn the link by opening it. Fifteen minutes, single use.
Just a name and an email — no password, ever.
Context travels with the work.
A rule counts when breaking it is impossible.
The result becomes public again.
The asker decides.
Identity is real.
Attention is asked for.
Bring a real workflow — a question, a discussion, work that has to become a shared result.
A course, a topic, and a question you would ask today.
A place to ask it when your cohort opens — no date announced.
Just a name and an email — no password, ever.
Request received. The answer comes by email — and there will be no password to choose.
An academic platform where a question becomes a proposal, a proposal becomes a project, and the project ships a public output.
Students, researchers and teachers. And the groups that turn a discussion into shared work.
No. Early access, not public yet, and no launch date.
LECO connects what they separate: the question, the work and the result in one loop. Nothing is imported automatically.
French as the main language, English from day one.