Rules

Help

If you cannot solve a challenge, make a question work item (issue) in this repository. The Academy team answers it. Help and questions gives the steps, and it gives the template that your work item must obey.

Channels

For every technical matter, use only these communication channels:

• Your merge requests, and the review that a Peer-Reviewer writes in them.
• The work items (issues) of the repository.
• The progress report.

A technical matter is a challenge, a solution, a review or a metric. Keep it in the repository. A chat or an email does not extend the knowledge of the Academy.

A Peer-Reviewer is a member of the Academy team. The other talents do not review your work, and you do not review theirs.

An administrative matter goes to [email protected]. These are the administrative cases:

Two matters go to your recruiter and not to that address:

• Your progress, if you are in the journey phase or the quest phase. Read End of the process.
• A contract that Fluid Attacks did not send you. Read Payment.

CAUTION: You must not communicate with the other talents in the Academy. You can read their work items and their merge requests, and you must not answer them. Fluid Attacks can remove you from the process if you do this.

AI

You can use an artificial intelligence (AI) tool in all the process. But you must be transparent about it.

If you use AI for a programming solution, you must record the tool in the comments of the prelude. Specific criteria gives the two lines that you write there, and it defines the prelude.

A ctf-hacking solution and a vbd-hacking solution have no declaration of AI. The Gherkin scenario of those solutions gives each command and each step of your work in detail.

CAUTION: Fluid Attacks does not accept a solution that a program made, with no human author and with no human review. Do not send the output of an AI tool as your solution.

Platforms

For programming challenges, Fluid Attacks supports two platforms at this time: CodeAbbey and SPOJ. Your policy permits one platform or the two platforms. Your policy also sometimes gives you a specific language. Policy explains how to read your policy.

To get unique solutions, Fluid Attacks recommends a language that few talents use. Languages gives the languages that the CI accepts, and the languages that Fluid Attacks removed.

Sites

For ctf-hacking challenges and vbd challenges, Fluid Attacks recommends that you read the data.yaml file in the policies folder. The file gives the sites that your policy permits. Policy explains how to read that file.

NOTE: Send each solution to the repository immediately after you solve the challenge. Do not keep your solutions and send them together later. When you send each solution immediately, you get feedback. The feedback shows your errors, and it can help you with the subsequent challenges. This instruction has more weight than the reference hour of Terms.